Apparatus and method for transmission of uplink control information in network cooperative communication

ABSTRACT

The disclosure relates to a communication technique and a system for integrating a 5G communication system with IoT technology to support a higher data transmission rate after a 4G system. The disclosure may be applied to intelligent services, based on 5G communication technology and IoT-related technologies (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and safety related services, etc.).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority under 35 U.S.C. 119 toKorean Patent Application No 10-2019-0100462 filed on Aug. 16, 2019,Korean Patent Application No. 10-2019-0126491 filed on Oct. 11, 2019,Korean Patent Application No. 10-2019-0133304 filed on Oct. 24, 2019,and Korean Patent Application No. 10-2020-0018624 filed on Feb. 14, 2020in the Korean Intellectual Property Office, the disclosures of which areherein incorporated by reference in their entirety.

BACKGROUND 1. Field

The disclosure relates to a wireless communication system and, moreparticularly, to a method and apparatus for transmitting uplink controlinformation to a plurality of transmission points/panels/beams by aterminal for cooperative communication between multiple transmissionpoints/panels/beams.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a “Beyond 4G Network” or a“Post LTE System”. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), full dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud radio access networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,coordinated multi-points (CoMP), reception-end interference cancellationand the like. In the 5G system, hybrid FSK and QAM modulation (FQAM) andsliding window superposition coding (SWSC) as an advanced codingmodulation (ACM), and filter bank multi carrier (FBMC), non-orthogonalmultiple access (NOMA), and sparse code multiple access (SCMA) as anadvanced access technology have also been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofeverything (IoE), which is a combination of the IoT technology and thebig data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing information technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, machine type communication (MTC), andmachine-to-machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud radioaccess network (RAN) as the above-described big data processingtechnology may also be considered an example of convergence of the 5Gtechnology with the IoT technology.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

The disclosure provides a method for transmitting uplink controlinformation to a plurality of transmission points/panels/beams by aterminal for network coordination in a wireless communication system.

In order to solve the above-described problem, an embodiments accordingto this disclosure comprise a method performed by a terminal in awireless communication system, the method comprising: receiving, from abase station, configuration information including information on atleast one repetition number and information on at least one transmissiontiming for hybrid automatic repeat request (HARQ) feedback transmission;receiving, from the base station, downlink control information (DCI)including information indicating one of the at least one transmissiontiming and information indicating one of the at least one repetitionnumber; receiving, from the base station, data in a plurality of firstslots based on a repetition number indicated by the DCI; andtransmitting, to the base station, HARQ feedback in a plurality ofsecond slots determined based on the plurality of first slots, whereinthe HARQ feedback is set to a negatively acknowledgement (NACK) in aslot other than a slot determined based on a transmission timingindicated by the DCI among the plurality of second slots.

In order to solve the above-described problem, an embodiments accordingto this disclosure comprise a method performed by a base station in awireless communication system, the method comprising: transmitting, to aterminal, configuration information including information on at leastone repetition number and information on at least one transmissiontiming for hybrid automatic repeat request (HARQ) feedback transmission;transmitting, to the terminal, downlink control information (DCI)including information indicating one of the at least one transmissiontiming and information indicating one of the at least one repetitionnumber; transmitting, to the terminal, data in a plurality of firstslots based on a repetition number indicated by the DCI; and receiving,from the terminal, HARQ feedback in a plurality of second slotsdetermined based on the plurality of first slots, wherein the HARQfeedback is set to a negatively acknowledgement (NACK) in a slot otherthan a slot determined based on a transmission timing indicated by theDCI among the plurality of second slots.

In order to solve the above-described problem, an embodiments accordingto this disclosure comprise a terminal in a wireless communicationsystem, the terminal comprising: a transceiver; and a controller coupledwith the transceiver and configured to: receive, from a base station,configuration information including information on at least onerepetition number and information on at least one transmission timingfor hybrid automatic repeat request (HARQ) feedback transmission,receive, from the base station, downlink control information (DCI)including information indicating one of the at least one transmissiontiming and information indicating one of the at least one repetitionnumber, receive, from the base station, data in a plurality of firstslots based on a repetition number indicated by the DCI, and transmit,to the base station, HARQ feedback in a plurality of second slotsdetermined based on the plurality of first slots, wherein the HARQfeedback is set to a negatively acknowledgement (NACK) in a slot otherthan a slot determined based on a transmission timing indicated by theDCI among the plurality of second slots.

In order to solve the above-described problem, an embodiments accordingto this disclosure comprise a base station in a wireless communicationsystem, the base station comprising: a transceiver, and a controllerconfigured to: transmit, to a terminal, configuration informationincluding information on at least one repetition number and informationon at least one transmission timing for hybrid automatic repeat request(HARQ) feedback transmission, transmit, to the terminal, downlinkcontrol information (DCI) including information indicating one of the atleast one transmission timing and information indicating one of the atleast one repetition number, transmit, to the terminal, data in aplurality of first slots based on a repetition number indicated by theDCI, and receive, from the terminal, HARQ feedback in a plurality ofsecond slots determined based on the plurality of first slots, whereinthe HARQ feedback is set to a negatively acknowledgement (NACK) in aslot other than a slot determined based on a transmission timingindicated by the DCI among the plurality of second slots.

According to the disclosure, when network coordination is used in awireless communication system, the time required for the terminal totransmit uplink control information to each transmissionpoint/panel/beam can be shortened.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or, the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 illustrates a view for a basic structure of a time-frequencydomain of a mobile communication system according to an embodiment;

FIG. 2 illustrates a view for explaining a frame, subframe and slotstructure of a mobile communication system according to an embodiment;

FIG. 3 illustrates an example of a configuration of a bandwidth part(BWP) in a wireless communication system according to an embodiment;

FIG. 4 illustrates a view for an example of configuring a control regionof a downlink control channel in a wireless communication systemaccording to an embodiment;

FIG. 5 illustrates a view for explaining the structure of a downlinkcontrol channel of a mobile communication system according to anembodiment,

FIG. 6 illustrates a view for a frequency axis resource allocationexample of a physical downlink shared channel (PDSCH) in a wirelesscommunication system according to an embodiment;

FIG. 7 illustrates a view for an example of time axis resourceallocation of a PDSCH in a wireless communication system according to anembodiment;

FIG. 8 illustrates a view for an example of time axis resourceallocation according to a subcarrier interval of a data channel and acontrol channel in a wireless communication system according to anembodiment;

FIG. 9 illustrates a view for a case in which multiple PUCCH resourcesfor HARQ-ACK transmission for a PDSCH overlap when multi-slot repetitionis not configured according to an embodiment;

FIG. 10 illustrates a view for a case where PUCCH resources overlap whenmulti-slot repetition is configured according to an embodiment;

FIG. 11 illustrates a view for a base station and a terminal radioprotocol structure when performing single cell, carrier aggregation, anddual connectivity according to an embodiment;

FIG. 12 illustrates a view for an example of an antenna portconfiguration and resource allocation for cooperative communicationaccording to some embodiments in a wireless communication systemaccording to an embodiment;

FIG. 13 illustrates a view for an example of downlink controlinformation (DCI) configuration for cooperative communication in awireless communication system according to an embodiment;

FIG. 14A illustrates a view for HARQ-ACK reporting for non-coherentjoint transmission (NC-JT) transmission according to an embodiment, FIG.14B is a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment, FIG. 14Cis a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment, and FIG.14D is a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment:

FIG. 15A illustrates a view for a case where overlap occurs betweenPUCCH resources according to an embodiment;

FIG. 15B illustrates a view a method of transmitting PUCCH when overlapoccurs between PUCCH resources according to an embodiment;

FIG. 16A illustrates a view for type 1 HARQ-ACK codebook methods foreach PDSCH repetitive transmission across multiple slots, a PDSCHrepetitive transmission within a single slot, and no repetitivetransmission according to an embodiment, FIG. 16B is a view illustratingtype 1 HARQ-ACK codebook methods for each PDSCH repetitive transmissionacross multiple slots, a PDSCH repetitive transmission within a singleslot, and no repetitive transmission according to an embodiment, andFIG. 16C is a view illustrating type 1 HARQ-ACK codebook methods foreach PDSCH repetitive transmission across multiple slots, a PDSCHrepetitive transmission within a single slot, and no repetitivetransmission according to an embodiment;

FIG. 17 illustrates a terminal structure in a wireless communicationsystem according to an embodiment; and

FIG. 18 illustrates a structure of a base station in a wirelesscommunication system according to an embodiment.

DETAILED DESCRIPTION

FIGS. 1 through 18, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

Hereinafter, embodiments of the disclosure will be described in detailwith reference to the accompanying drawings.

In describing embodiments of the disclosure, descriptions related totechnical contents well-known in the art and not associated directlywith the disclosure will be omitted. Such an omission of unnecessarydescriptions is intended to prevent obscuring of the main idea of thedisclosure and more clearly transfer the main idea.

For the same reason, in the accompanying drawings, some elements may beexaggerated, omitted, or schematically illustrated. Further, the size ofeach element does not completely reflect the actual size. In thedrawings, identical or corresponding elements are provided withidentical reference numerals.

The advantages and features of the disclosure and ways to achieve themwill be apparent by making reference to embodiments as described belowin detail in conjunction with the accompanying drawings. However, thedisclosure is not limited to the embodiments set forth below, but may beimplemented in various different forms. The following embodiments areprovided only to completely disclose the disclosure and inform thoseskilled in the art of the scope of the disclosure, and the disclosure isdefined only by the scope of the appended claims. Throughout thespecification, the same or like reference numerals designate the same orlike elements.

Here, it will be understood that each block of the flowchartillustrations, and combinations of blocks in the flowchartillustrations, can be implemented by computer program instructions.These computer program instructions can be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions specified in the flowchart block or blocks.These computer program instructions may also be stored in a computerusable or computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Further, each block of the flowchart illustrations may represent amodule, segment, or portion of code, which includes one or moreexecutable instructions for implementing the specified logicalfunction(s). It should also be noted that in some alternativeimplementations, the functions noted in the blocks may occur out of theorder. For example, two blocks shown in succession may in fact beexecuted substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved.

As used herein, the “unit” refers to a software element or a hardwareelement, such as a Field Programmable Gate Array (FPGA) or anApplication Specific Integrated Circuit (ASIC), which performs apredetermined function. However, the “unit” does not always have ameaning limited to software or hardware. The “unit” may be constructedeither to be stored in an addressable storage medium or to execute oneor more processors. Therefore, the “unit” includes, for example,software elements, object-oriented software elements, class elements ortask elements, processes, functions, properties, procedures,sub-routines, segments of a program code, drivers, firmware,micro-codes, circuits, data, database, data structures, tables, arrays,and parameters. The elements and functions provided by the “unit” may beeither combined into a smaller number of elements, or a “unit”, ordivided into a larger number of elements, or a “unit”. Moreover, theelements and “units” or may be implemented to reproduce one or more CPUswithin a device or a security multimedia card. Further, the “unit” inthe embodiments may include one or more processors.

Hereinafter, the operation principle of the disclosure will be describedin detail in conjunction with the accompanying drawings. In thefollowing description of the disclosure, a detailed description of knownfunctions or configurations incorporated herein will be omitted when itmay make the subject matter of the disclosure rather unclear. The termswhich will be described below are terms defined in consideration of thefunctions in the disclosure, and may be different according to users,intentions of the users, or customs. Therefore, the definitions of theterms should be made based on the contents throughout the specification.Hereinafter, the base station is a subject that performs resourceallocation of a terminal, and may be at least one of a gNode B (gNB), aneNode B (eNB), a Node B, a base station (BS), a radio access unit, abase station controller, or a node on a network. The terminal mayinclude a user equipment (LE), a mobile station (MS), a cellular phone,a smart phone, a computer, or a multimedia system capable of performingcommunication functions. Of course, it is not limited to the aboveexample. Hereinafter, the disclosure describes a technique for aterminal to receive broadcast information from a base station in awireless communication system. The disclosure relates to a communicationtechnique and a system for integrating a 5th generation (5G)communication system with an Internet of Things (IoT) technology tosupport a higher data transfer rate after a 4th generation (4G) system.The disclosure may be applied to intelligent services (e.g., smart home,smart building, smart city, smart car or connected car, health care,digital education, retail, security and safety related services, etc.),based on 5G communication technology and IoT-related technologies.

In the following description, terms referring to broadcast information,terms referring to control information, terms associated withcommunication coverage, terms referring to state changes (e.g, event),terms referring to network entities, terms referring to messages, termsreferring to device elements, and the like are illustratively used forthe sake of convenience. Therefore, the disclosure is not limited by theterms as used below, and other terms referring to subjects havingequivalent technical meanings may be used.

In the following description, the disclosure uses terms and namesdefined in 3rd generation partnership project long term evolution (3GPPLTE) standards for the convenience of description. However, thedisclosure is not limited by these terms and names, and may be appliedin the same way to systems that conform other standards.

The wireless communication system has evolved into a broadband wirelesscommunication system that provides high-speed and high-quality packetdata services using communication standards, such as high-speed packetaccess (HSPA) of 3GPP, long-term evolution (LTE) or evolved universalterrestrial radio access (E-UTRA), LTE-advanced (LTE-A), LTE-Pro,high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), andIEEE 802.16e, etc., rather than providing initial voice-based services.

As a representative example of a broadband wireless communicationsystem, in an LTE system, an orthogonal frequency division multiplexing(OFDM) scheme is adopted in downlink (DL), and a single carrierfrequency division multiple access (SC-OFDM) scheme is adopted in uplink(UL). The uplink refers to a radio link through which a terminal (userequipment (UE) or mobile station (MS) transmits data or control signalsto a base station (eNode B, or base station (BS)), and the downlinkrefers to a radio link through which a base station transmits data orcontrol signals to a terminal. In such a multiple access method, data orcontrol information of each user is usually divided by assigning andoperating so that time-frequency resources to which data or controlinformation to be carried for each user do not overlap, that is,orthogonality is established.

As a future communication system after LTE, that is, a 5G communicationsystem should be able to freely reflect various requirements of usersand service providers, so service satisfying various requirements shouldbe supported. Services considered for 5G communication systems includeenhanced mobile broadband (eMBB), massive machine type communication(mMTC), and ultra-reliability low latency communication (URLLC), and soon.

According to some embodiments, the eMBB aims to provide a more improveddata transmission rate than the existing LTE, LTE-A or LTE-Pro. Forexample, in a 5G communication system, the eMBB should be able toprovide a maximum data rate of 20 Gbps in the downlink and a maximumdata rate of 10 Gbps in the uplink from the perspective of one basestation. At the same time, the actual perceived data rate of theincreased terminal should be provided. In order to satisfy thisrequirement, it is required to improve transmission/reception technologyincluding a more advanced multi input multi output (MIMO) transmissiontechnology. Also, it is possible to satisfy the data transmission speedrequired by the 5G communication system by using a wider bandwidth than20 MHz in the 3-6 GHz or 6 GHz or higher frequency band, instead of the2 GHz band used by the current LTE.

At the same time, mMTC is being considered to support applicationservices such as the Internet of Things (IoT) in 5G communicationsystems. In order to efficiently provide the Internet of Things, mMTCmay be required to support access to a large-scale terminal within acell, improve the coverage of the terminal, improve battery time, andreduce the cost of the terminal. The Internet of Things should be ableto support a large number of terminals (e.g., 1,000,000 terminals/km2)in a cell, as the cell is attached to various sensors and variousdevices to provide communication functions. In addition, because of thenature of the service, the terminal supporting mMTC is likely to belocated in a shaded area that cannot be covered by a cell, such as thebasement of a building, and thus may require wider coverage than otherservices provided by a 5G communication system. Since the terminalsupporting mMTC should be configured with a low-cost terminal, and it isdifficult to frequently replace the battery of the terminal, a very longbattery lifetime may be required.

Finally, URLLC, which is a cellular-based wireless communication serviceused for a specific purpose (mission-critical), is a service that isused for remote control of robots or mechanical devices, industrialautomation, unmanned aerial vehicles, remote health control, emergencynotifications, etc., and should provide communication providingultra-low latency and ultra-high reliability. For example, a servicesupporting URLLC should satisfy an air interface latency of less than0.5 milliseconds and at the same time has a requirement of a packeterror rate of 10-5 or less. Therefore, for a service supporting URLLC, a5G system needs to provide a smaller transmit time interval (TTI) thanother services, and at the same time, a design requirement is requiredto allocate a wide resource in a frequency band. However, theabove-described mMTC, URLLC, and eMBB are only examples of differentservice types, and the service types to which the disclosure is appliedare not limited to the above-described examples. The services consideredin the above-mentioned 5G communication system should be provided bybeing fused with each other on the basis of one framework. That is, forefficient resource management and control, it is preferable that eachservice is integrated and controlled and transmitted as one systemrather than being operated independently.

In addition, hereinafter, embodiments will be described as examples ofan LTE, LTE-A, LTE Pro, or NR system, but the embodiments may be appliedto other communication systems having similar technical backgrounds orchannel types. In addition, the embodiments may be applied to othercommunication systems through some modifications within a range notsignificantly departing from the scope of the disclosure as judged by aperson having skilled technical knowledge.

The disclosure relates to a method and an apparatus for reportingchannel state information to increase power saving efficiency of aterminal in a wireless communication system.

According to the disclosure, when the terminal operates in the powersaving mode in the wireless communication system, the power savingeffect may be further improved by optimizing the channel stateinformation reporting method accordingly.

Hereinafter, the frame structure of the 5G system will be described inmore detail with reference to the drawings.

FIG. 1 illustrates a view for a basic structure of a time-frequencydomain of a mobile communication system according to an embodiment.

Referring to FIG. 1, the horizontal axis represents a time domain, andthe vertical axis represents a frequency domain. The basic unit in thetime and frequency domains is a resource element (RE) 1-01 and may bedefined as 1 orthogonal frequency division multiplexing (OFDM) symbol1-02 in the time axis and 1 subcarrier 1-03 in the frequency axis. Inthe frequency domain, N_sc{circumflex over ( )}RB (e.g., 12) consecutiveREs may constitute one resource block (RB) 1-04. In an embodiment, aplurality of OFDM symbols may constitute one subframe 1-10.

FIG. 2 illustrates a view for explaining a frame, subframe and slotstructure of a next generation mobile communication system according toan embodiment.

Referring to FIG. 2, one frame 2-00 may be composed of one or moresubframes 2-01, and one subframe may be composed of one or more slots2-02. As an example, one frame 2-00 may be defined as 10 milli-seconds(ms). One subframe 2-01 may be defined as 1 ms, and in this case, oneframe 2-00 may consist of a total of 10 subframes 2-01. One slot 2-02,2-03 may be defined by 14 OFDM symbols (i.e., the number of symbols perslot (N_(symb) ^(slot))=14). One subframe 2-01 may be composed of one ora plurality of slots 2-02, 2-03, the number of slots 2-02, 2-03 persubframe 2-01 may be different depending on the configuration value μ2-04, 2-05 for the subcarrier spacing. In the example of FIG. 2, thecase where the subcarrier spacing is configured is μ=0 (2-04) and μ=1(2-05). When μ=0 (2-04), one subframe 2-01 may consist of one slot 2-02,and when μ=1 (2-05), one subframe 2-01 may be composed of two slots2-03. That is, the number of slots per subframe (N_(slot) ^(subframe,μ))may vary according to the configuration value μ for the subcarrierspacing, and thus the number of slots (N_(slot) ^(frame,μ)) per framemay vary. The N_(slot) ^(subframe,μ) and N_(slot) ^(frame,μ) accordingto each subcarrier spacing configuration p may be defined as in [Table1] below.

TABLE 1 μ N_(symb) ^(slot) N_(slot) ^(frame,μ) N_(slot) ^(subframeμ) 014 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16 5 14 320 32

In NR, one component carrier (CC) or serving cell may be configured withup to 250 or more RBs. Therefore, when the terminal always receives theentire serving cell bandwidth (LTE), such as LTE, the power consumptionof the terminal may be extreme, and in order to solve this, the basestation may configure one or more bandwidth parts (BWP) for theterminal, in order to support the terminal to change the reception areain the cell. In the NR, the base station may configure the ‘initialBWP’, which is the bandwidth of CORESET #0 (or common search space, CSS)for the terminal through the master information block (MIB). Then, thebase station may configure the initial BWP (first BWP) of the terminalthrough radio resource control (RRC) signaling, and may notify theterminal of at least a piece of BWP configuration information that maybe indicated through downlink control information (DCI) in the future.Thereafter, the base station may indicate which band the terminal willuse by notifying the BWP ID through DCI. If the terminal cannot receiveDCI from the currently allocated BWP for a specific time or more, theterminal may return to ‘default BWP’ and try to receive DCI.

FIG. 3 illustrates a view for an example of a configuration of abandwidth part (BWP) in a wireless communication system according to anembodiment.

Referring to FIG. 3, FIG. 3 illustrates an example in which the terminalbandwidth (3-00) is configured to have two bandwidth portions, namely,the bandwidth portion #1 (3-05) and the bandwidth portion #2 (3-10). Thebase station may configure one or a plurality of bandwidth portions forthe terminal, and may configure information as shown in [Table 2] belowfor each bandwidth portion.

TABLE 2 BWP ::=          SEQUENCE {  bwp-Id           BWP-Id,  (Bandwidth part identifier)  locationAndBandwidth     INTEGER(1..65536),  (Bandwidth part location)  subcarrierSpacing      ENUMERATED {n0, n1, n2, n3, n4, n5},  cyclicPrefix        ENUMERATED { extended }    }

Of course, the disclosure is not limited to the above-described example,and various parameters related to the bandwidth part may be configuredfor the terminal in addition to the above-described configurationinformation. The above-described information may be transmitted to theterminal by the base station through higher layer signaling, forexample, RRC signaling. At least one bandwidth portion among theconfigured one or multiple bandwidth portions may be activated. Whetherto activate the configured bandwidth part may be transmittedsemi-statically through RRC signaling from the base station to theterminal, or may be dynamically transmitted through a MAC controlelement (CE) or DCI.

According to an embodiment, a terminal before a radio resource control(RRC) connection may receive an initial bandwidth part (initial BWP) forinitial access from a base station through a master information block(MIB). More specifically, in order to receive the system information(remaining system information; may correspond to RMSI or systeminformation block (SIB) 1) required for initial access through the MIBin the initial access step, the terminal may receive configurationinformation for the control area (control resource set, CORSET) and thesearch space through which the PDCCH may be transmitted. The controlarea and the search space configured by the MIB may be regarded asidentifier (ID) 0, respectively.

The base station may notify the terminal of configuration informationsuch as frequency allocation information, time allocation information,and numerology for the control area #0 through the MIB. In addition, thebase station may notify the terminal of the configuration informationfor the monitoring period and occasion for the control area #0 throughthe MIB, that is, the configuration information for the search space #0.The terminal may regard the frequency domain configured as the controlarea #0 obtained from the MIB as an initial bandwidth part for initialaccess. At this time, the identifier (ID) of the initial bandwidth partmay be regarded as 0.

The bandwidth parts supported by the above-described next-generationmobile communication system (5G or NR system) may be used for variouspurposes.

For example, when the bandwidth supported by the terminal is smallerthan the system bandwidth, the bandwidth supported by the terminal maybe supported through configuring the bandwidth portion. For example, inTable 2, the frequency location (configuration information 2) of thebandwidth portion is configured for the terminal, so that the terminalmay transmit and receive data at a specific frequency location withinthe system bandwidth.

As another example, for the purpose of supporting different numerology,the base station may configure a plurality of bandwidth portions for theterminal. For example, in order to support data transmission andreception using a subcarrier spacing of 15 kHz and a subcarrier spacingof 30 kHz to arbitrary terminals, two bandwidth portions may beconfigured to use subcarrier spacings of 15 kHz and 30 kHz,respectively. Different bandwidth parts may be frequency divisionmultiplexing (FDM), and when data is to be transmitted/received at aspecific subcarrier spacing, a bandwidth part configured at acorresponding subcarrier spacing may be activated.

As another example, for the purpose of reducing power consumption of theterminal, the base station may configure a bandwidth portion havingdifferent sizes of bandwidth for the terminal. For example, if theterminal supports a very large bandwidth, for example, a bandwidth of100 MHz, and always transmits/receives data with the correspondingbandwidth, the large bandwidth may cause very large power consumption.In particular, it is very inefficient in terms of power consumption forthe terminal to perform monitoring of an unnecessary downlink controlchannel for a large bandwidth of 100 MHz in a situation where there isno traffic. Therefore, for the purpose of reducing power consumption ofthe terminal, the base station may configure a bandwidth portion of arelatively small bandwidth for the terminal, for example, a bandwidthportion of 20 mega-Hertz (MHz). In a situation where there is notraffic, the terminal may perform a monitoring operation in the 20 MHzbandwidth portion, and when data occurs, may transmit/receive data usingthe 100 MHz bandwidth portion according to the instructions of the basestation.

In the method of configuring the above-described bandwidth part,terminals before the RRC connection may receive the configurationinformation for the initial bandwidth part through the masterinformation block (MTB) in the initial access step. More specifically,the terminal may receive, from the MIB of the physical broadcast channel(PBCH), a control area (control resource set (CORESET)) for a downlinkcontrol channel through which a downlink control information (DCI)scheduling a system information block (SIB) may be transmitted. Thebandwidth of the control area configured as the MIB may be regarded asan initial bandwidth part, and the terminal may receive a PDSCH throughwhich SIB is transmitted through the configured initial bandwidth part.The initial bandwidth part may be used for other system information(OSI), paging, and random access, in addition to the purpose ofreceiving the SIB. Hereinafter, a synchronization signal (SS)/PBCH blockof a next generation mobile communication system (5G or NR system) willbe described.

The SS/PBCH block may mean a physical layer channel block composed of aprimary SS (PSS), a secondary SS (SSS), and a PBCH. More specifically,the SS/PBCH block may be defined as follows.

-   -   PSS: A signal that is a reference for downlink time/frequency        synchronization, and may provide some information of a cell ID.    -   SSS: SSS is a reference for downlink time/frequency        synchronization, and may provide remaining cell ID information        not provided by the PSS. Additionally, the SSS may serve as a        reference signal for demodulation of the PBCH.    -   PBCH: PBCH makes it possible to provide essential system        information necessary for transmitting/receiving data channels        and control channels of the terminal. The essential system        information may include search space related control information        indicating radio resource mapping information of a control        channel, scheduling control information for a separate data        channel transmitting system information, and the like.    -   SS/PBCH block: The SS/PBCH block may consist of a combination of        PSS, SSS and PBCH. One or more SS/PBCH blocks may be transmitted        within 5 ms, and each SS/PBCH block transmitted may be        distinguished by an index.

The terminal may detect PSS and SSS in the initial access stage anddecode PBCH. The terminal may acquire MIB from the PBCH, and may receivecontrol area #0 through the MIB. The terminal may perform monitoring forthe control area #0, assuming that the selected SS/PBCH block and thedemodulation reference signal (DMRS) transmitted from the control area#0 are quasi co location (QCL). The terminal may receive systeminformation as downlink control information transmitted from the controlarea #0. The terminal may obtain random access channel (RACH) relatedconfiguration information necessary for initial access from the receivedsystem information. The terminal may transmit a physical RACH (PRACH) tothe base station in consideration of the selected SS/PBCH index, and thebase station receiving the PRACH may acquire information on the SS/PBCHblock index selected by the terminal. It may be seen that the basestation selects a certain block from each SS/PBCH block, and monitorsthe control area #0 corresponding to (or associated with) the SS/PBCHblock selected by the terminal.

Hereinafter, downlink control information (hereinafter referred to asDCI) in a next-generation mobile communication system (5G or NR system)will be described in detail.

In a next-generation mobile communication system (5G or NR system),scheduling information for uplink data (or physical uplink sharedchannel (PUSCH)) or scheduling information for downlink data (orphysical downlink shared channel (PDSCH)) may be transmitted from a basestation to a terminal through DCI. The terminal may monitor the DCIformat for fallback and the DCI format for non-fallback for PUSCH orPDSCH. The fallback DCI format may be composed of a predetermined fixedfield between the base station and the terminal, and the DCI format fornon-fallback may include a configurable field.

DCI may be transmitted through a physical downlink control channel(PDCCH) through a channel coding and modulation process. Cyclicredundancy check (CRC) may be attached to the DCI message payload, andthe CRC may be scrambled with a radio network temporary identifier(RNTI) corresponding to the identity of the terminal. Different RNTIsmay be used for scrambling the CRC attached to the payload of the DCImessage, depending on the purpose of the DCI message, for example,terminal-specific (UE-specific) data transmission, power control commandor random access response. That is, the RNTI is not explicitlytransmitted, but may be included in the CRC calculation process andtransmitted. When the DCI message transmitted on the PDCCH is received,the terminal may identify the CRC using the allocated RNTI. If the CRCidentification result is correct, the terminal may know that thecorresponding message has been transmitted to the terminal.

For example, DCI scheduling a PDSCH for system information (SI) may bescrambled with SI-RNTI. The DCI scheduling the PDSCH for the randomaccess response (RAR) message may be scrambled with RA-RNTI. The DCIscheduling the PDSCH for the paging message may be scrambled withP-RNTI. DCI notifying of the slot format indicator (SFI) may bescrambled with SFI-RNTI. DCI notifying of transmit power control (TPC)may be scrambled with TPC-RNTI. The DCI for scheduling theterminal-specific PDSCH or PUSCH may be scrambled with cell RNTI(C-RNTI).

DCI format 0_0 may be used as a fallback DCI scheduling PUSCH, and atthis time, CRC may be scrambled with C-RNTI. In one embodiment, DCIformat 0_0 in which CRC is scrambled with C-RNTI may include informationas shown in [Table 3] below.

TABLE 3 Indicator for DCI formats - [1] bit Frequency domain resourceassignment [┌log₂(N_(RB) ^(12,BWP)(N_(RB) ^(ULBWP)+1)┐ _(bits) Timedomain resource assignment - X bits Frequency hopping flag - 1 bitModulation and coding scheme - 5 bits New data indicator - 1 bitRedundancy version - 2 bits HARQ process number - 4 bits TPC command forscheduled PUSCH - 2 bits UL/SUL indicator - 0 or 1 bit

DCI format 0_1 may be used as a non-fallback DCI scheduling PUSCH, andthe CRC may be scrambled with C-RNTI. In an embodiment, DCI format 0_1in which CRC is scrambled with C-RNTI may include information as shownin [Table 4] below.

TABLE 4  Carrier indicator-0 or 3 bits  UL/SUL-0 or 1 bit  Identifierfor DCI formats-[1] bits  Bandwidth part indicator-0, 1, or 2 bits Frequency domain resource assignment For resource allocation type 0,┌N_(RB) ^(UL,BWP)/P)┐ bits  For resource allocation type 1, ┌log₂(N_(RB)^(UL,BWP)(N_(RB) ^(UL,BWP) + 1)/2)┐ bits  Time domain resourceassignment-1, 2, 3, or 4 bits  VRB-to-PRB mapping to physical resourceblock mapping-0 or  1 bit, only resource allocation type 1  0 bits ifonly resource allocation type 0 is configured;  1 bit otherwise Frequency hopping flag-0 or 1 bit only for resource allocation type 1 0 bits if only resource allocation type 0 is configured;  1 bitotherwise  Modulation and coding scheme-5 bits  New data indicator-1 bit Redundancy version-2 bits  HARQ process number-4 bits  1^(st) downlinkassignment index-1 or 2 bits  0 bits for semi-static HARQ-ACK codebook; 2 bits for dynamic HARQ-ACK codebook with single  HARQ-ACK codebook. 2^(nd) downlink assignment index-0 or 2 bits  2 bits for dynamicHARQ-ACK codebook with two  HARQ-ACK sub-codebooks;  0 bits otherwise TPC command for scheduled PUSCH-2 bits  ${SRS}\mspace{14mu}{resource}\mspace{14mu}{indicator}\text{-}\left\lceil {\log_{2}\left( {\sum\limits_{k = 1}^{L_{\max}}\;\begin{pmatrix}N_{SRS} \\k\end{pmatrix}} \right)} \right\rceil\mspace{14mu}{or}\mspace{14mu}\left\lceil {\log_{2}\left( N_{SRS} \right)} \right\rceil\mspace{14mu}{bits}$ $\left\lceil {\log_{2}\left( {\sum\limits_{k = 1}^{L_{\max}}\;\begin{pmatrix}N_{SRS} \\k\end{pmatrix}} \right)} \right\rceil\mspace{11mu}\text{bits for non-codebook based PUSCH transmission;}$ ┌log₂(N_(SRS))┐ bits for codebook based PUSCH transmission.  Precodinginformation and number of layers-up to 6 bits  Antenna ports-up to 5bits  SRS request-2 bits  CSI request-0, 1, 2, 3, 4, 5, or 6 bits  CBGtransmission information-0, 2, 4, 6, or 8 bits  PTRS-DMRS association-0or 2 bits  Beta offset indicator-0 or 2 bits  DMRS sequenceinitialization-0 or 1 bit

DCI format 1_0 may be used as a fallback DCI for scheduling the PDSCH,and the CRC may be scrambled with C-RNTI. In an embodiment. DCI format1_0 in which the CRC is scrambled with C-RNTI may include information asshown in [Table 5] below.

TABLE 5 Indicator for DCI formats - [1] bit Frequency domain resourceassignment [┌log₂(N_(RB) ^(UL,BWP) (N_(RB) ^(UL,BWP) + 1)/2)┐] bits Timedomain resource assignment - X bits VRB-to-PRB mapping - 1 bitModulation and coding scheme - 5 bits New data indicator - 1 bitRedundancy version - 2 bits HARQ process number - 4 bits Down kinkassignment index - 2 bits TPC command for scheduled PUSCH - [2] bitsPUCCH resource indicator - 3 bits PDSCH-to-HARQ feedback timingindicator - [3] bits

DCI format 1_1 may be used as a non-fallback DCI for scheduling a PDSCH,where CRC may be scrambled with C-RNTI. In an embodiment, DCI format 1_1in which CRC is scrambled by C-RNTI may include information as shown in[Table 6] below.

TABLE 6 Carrier indicator - 0 or 3 bits Identifier for DCI formats - [1]bits Bandwidth part indicator - 0, 1, or 2 bits Frequency domainresource assignment For resouce allocation type 1, ┌N_(RB) ^(UL,BWP)/P┐bits For resource allocation type 1, [┌log₂(N_(RB) ^(UL,BWP) (N_(RB)^(UL,BWP) + 1)/2)┐] bits Time domain resource assignment - 1, 2, 3, or 4bits VRB-to-PRB mapping - 0 or 1 bit, only resource allocation type 1 0bits if only resource allocation type 0 is configured; 1 bit otherwisePRB bundling size indicator - 0 or 1 bit Rate matching indicator - 0, 1,or 2 bits ZP CSI-RS trigger - 0, 1, or 2 bits For transport block 1:Modulation and coding scheme - 5 bits New data indicator - 1 bitRedundancy version - 2 bits For transport block 2: Modulation and codingscheme - 5 bits New data indicator - 1 bit Redundancy version - 2 bitsHARQ process number - 4 bits Downlink assignment index - 0 or 2 or 4bits TPC command for scheduled PUSCH - 2 bits PUCCH resource indicator -3 bits PDSCH-to-HARQ feedback timing indicator - 3 bits Antenna ports -4, 5, or 6 bits Transmission configuration indication - 0 or 3 bits SRSrequest - 2 bits CBG transmission information - 0, 2, 4, 6, or 8 bitsCGB flushing out information - 0 or 1 bit DMRS sequence initialization -0 or 1 bit

FIG. 4 illustrates a view for an example of configuring a control areaof a downlink control channel in a next generation mobile communicationsystem according to an embodiment. That is, FIG. 4 is a viewillustrating an embodiment of a control area (control resource set(CORESET)) in which a downlink control channel is transmitted in a 5Gwireless communication system according to an embodiment.

Referring to FIG. 4, FIG. 4 illustrates an embodiment in which twocontrol areas (control area #1 4-01 and control area #2 4-02) areconfigured in one slot 4-20 within the bandwidth part of the terminal(UE bandwidth part) 4-10 and on the frequency axis, within one slot 4-20on the time axis. The control areas 4-01 and 4-02 may be configured as aspecific frequency resource 4-03 within the entire terminal bandwidthpart 4-10 on the frequency axis. The control areas 4-01 and 4-02 may beconfigured as one or a plurality of OFDM symbols on the time axis, whichmay be defined as a control resource set duration (4-04). Referring toFIG. 4, control area #1 (4-01) may be configured as a control resourceset duration of 2 symbols, and control area #2 (4-02) may be configuredas a control resource set duration of 1 symbol.

The control area in the above-described next-generation mobilecommunication system (5G or NR system) may be configured by the basestation performing higher layer signaling (e.g., system information,master information block (MIB), radio resource control (RRC) signaling)to the terminal. Configuring a control area to a terminal meansproviding information such as a control area identifier, a frequencylocation of the control area, and a symbol length of the control area.For example, the configuration for the control area may includeinformation as shown in [Table 7] below.

TABLE 7   ControlResourceSet ::=          SEQUENCE {00Correspod to L1parameter ‘CORESET-ID’  ControlResourceSetId         ControlResourceSetId, (Control area identity)frequencyDomainResources        BIT STRING (SIZE (45)), (frequencydomain allocation information) Duration        INTEGER(1..maxCoReSetDuration), (Time axis allocation information)Cce-REG-MappingType            CHOICE { (CCE-to-REG mapping scheme)Interleaved        SEQUENCE {  reg-BundleSize        ENUMERATED {n2, n3,n6},  precoderGranularity       ENUMERATED {SameAsREG bundle,allCntiguousRBs}  interleaverSize        ENUMERATED {n2, n3, n6}, shiftIndex  INTEGER (0...maxNrofPhysicalResoueceBlocks-1)  (interleaveshift) }, nonInterleaved        NULL },  tci-StatesPDCCH       S           EQUENCE (SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId   OPTIONAL, (QCL configuration information)  Tci-PresentInDCI    ENUMERATED {enabled}  }

In [Table 7], tci-StatesPDCCH (hereinafter referred to as “TCI state”)configuration information may include information of one or moresynchronization signal (SS)/physical broadcast channel (PBCH) index orchannel state information reference signal (CSI-RS) index in a quasi colocated (QCL) relationship with a demodulation reference signal (DMRS)transmitted in the corresponding control area. In addition, thetci-StatesPDCCH configuration information may include information onwhat the QCL relationship is. For example, the configuration of the TCIstate may include information as shown in [Table 8] below.

TABLE 8   TCI-State ::=           SEQUENCE {  tci-StateId            , qci-Type1             QCL-Info,  qci-Type2            QCL-Info     Optional  . . . } ,  QCL-Info ::=         SEQUENCE {   cell (cellindex)           ServiceCellIndex  Optional   bwp-Id (BWP index)        BWP-Id      Optional   referenceSignal (reference RS index) CHOICE {    csi-rs               NZP-CSI-RS-RecourceId,    ssb               SSB-Index,   },   qc1-Type               ENUMERATED{typeA, typeB, typeC, typeD   . . . }

Referring to the TCI state configuration, the cell index of thereference RS and/or the BWP index and the QCL type may be configuredtogether with the index of the reference RS in the QCL relationship,that is, the SS/PBCH block index or the CSI-RS index. The QCL typeindicates channel characteristics that are assumed to be shared betweenthe reference RS and the control area DMRS, and the examples of possibleQCL types are as follows.

-   -   QCL typeA: Doppler shift, Doppler spread, average delay, delay        spread.    -   QCL typeB: Doppler shift, Doppler spread.    -   QCL typeC: Doppler shift, average delay.    -   QCL typeD: Spatial Rx parameter.

The TCI state may be similarly configured for the control area DMRS aswell as other target RSs, such as PDSCH DMRS and CSI-RS, but a detaileddescription thereof will be omitted so as not to obscure the subjectmatter of the description.

FIG. 5 illustrates a view for explaining the structure of a downlinkcontrol channel of a next generation mobile communication systemaccording to an embodiment. That is, FIG. 5 is a view illustrating anexample of a basic unit of time and frequency resources configuring adownlink control channel that may be used in 5G according to anembodiment.

Referring to FIG. 5, a basic unit of time and frequency resourcesconstituting a control channel may be defined as a resource elementgroup (REG) 5-03. REG 5-03 may be defined as 1 OFDM symbol 5-01 on thetime axis, 1 physical resource block (PRB) 5-02 on the frequency axis,that is, 12 subcarriers. The base station may configure a downlinkcontrol channel allocation unit by connecting REGs 5-03.

As illustrated in FIG. 5, when a basic unit to which a downlink controlchannel is allocated in 5G is called a control channel element (CCE)5-04, 1 CCE 5-04 may consist of a plurality of REGs 5-03. For example,the REG 5-03 shown in FIG. 5 may be composed of 12 REs, and if 1 CCE5-04 is composed of 6 REGs 5-03, 1 CCE 5-04 may consist of 72 REs. Whena downlink control area is configured, the corresponding area may becomposed of a plurality of CCEs 5-04, and a specific downlink controlchannel may be transmitted by being mapped to one or a plurality of CCEs5-04 according to the aggregation level (AL) in the control area. TheCCEs 5-04 in the control area are divided into numbers, and the numbersof the CCEs 5-04 may be assigned according to a logical mapping method.

The basic unit of the downlink control channel shown in FIG. 5, that is,REG 5-03, may include both DCI mapped REs to which DCI is mapped and anarea to which the reference signal DMRS 5-05, which is a referencesignal for decoding, is mapped. As shown in FIG. 5, three DMRSs 5-05 maybe transmitted in 1 REG 5-03. The number of CCEs required to transmitthe PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level(AL), and the number of different CCEs may be used to implement linkadaptation of a downlink control channel. For example, when AL=L, onedownlink control channel may be transmitted through L CCEs.

The terminal should detect a signal without knowing the information onthe downlink control channel, and a search space indicating a set ofCCEs for blind decoding may be defined. The search space is a set ofdownlink control channel candidates composed of CCEs that the terminalshould attempt decoding on a given aggregation level. Since there arevarious aggregation levels that make a bundle of 1, 2, 4, 8, and 16CCEs, the terminal may have a plurality of search spaces. The searchspace set may be defined as a set of search spaces at all configuredaggregation levels.

The search space may be classified into a common search space and aterminal-specific search space. According to an embodiment, a certaingroup of terminals or all terminals may examine a common search space ofthe PDCCH in order to receive control information common to cells suchas dynamic scheduling or paging messages for system information.

For example, the terminal may receive PDSCH scheduling allocationinformation for transmission of the SIB including the operatorinformation of the cell by examining the common search space of thePDCCH. In the case of the common search space, since a certain group ofterminals or all terminals should receive the PDCCH, the common searchspace may be defined as a set of predetermined CCEs. Meanwhile, theterminal may receive scheduling allocation information for theterminal-specific PDSCH or PUSCH by examining the terminal-specificsearch space of the PDCCH. The terminal-specific search space may beterminal-specifically defined as a function of the identity of theterminal and various system parameters.

In 5G, parameters for the search space for the PDCCH may be configuredfrom the base station to the terminal by higher layer signaling (e.g.,SIB, MIB, RRC signaling). For example, the base station may configurethe number of PDCCH candidate groups at each aggregation level L, themonitoring period for the search space, the monitoring occasion insymbol units in the slot for the search space, the search space type(common search space or terminal-specific search space), the combinationof the DCI format and RNTI to be monitored in the search space, acontrol area index to monitor the search space, etc., for the terminal.For example, the above-described configuration may include informationsuch as [Table 9] below.

TABLE 9   SearchSpace ::=         SEQUENCE {   -- Identity of the searchspace.      SearchSpaceId = 0 identifies the    SearchSpace configuredvia PBCH (MIB) or ServingCellConfigCommon.   searchSpaceId            SearchSpaceId,   (search space identifier)  controlResourceSetId         ,   (control area identifier)  monitoringSlotPeriodicityAndOffset       CHOICE {   (monitoring slotlevel period)    sl1                NULL,    sl2                INTEGER(0...1),    sl4                INTEGER (0...3),    sl5             INTEGER (0...4),    sl8                INTEGER (0...7),   sl10               INTEGER (0...9),    sl16               INTEGER(0...15),    sl20               INTEGER (0...19)   }   duration(monitoring duration)      INTEGER (2...2559)  monitoringSymbolsWithinSlot          BIT STRING (SIZE (14))  (monitoring symbol within slot)   nrofCandidates            SEQUENCE {  (number of PDCCH candidates by aggregation level)   aggregationLevel1           ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},  aggregationLevel2           ENUMERATED {n0, n1, n2, n3, n4, n5, n6,n8},   aggregationLevel4           ENUMERATED {n0, n1, n2, n3, n4, n5,n6, n8},   aggregationLevel8           ENUMERATED {n0, n1, n2, n3, n4,n5, n6, n8},   aggregationLevel16          ENUMERATED {n0, n1, n2, n3,n4, n5, n6, n8},   },   searchSpaceType            CHOICE {   (searchspace type)   -- Configures this search space as common search space(CSS) and DCI formats to monitor.   common               SEQUENCE {  (common search space)   }   Ue-Specific              SEQUENCE {  (terminal-specific search space)   -- Indicates whether the UEmonitors in this USS for DCI formats 0-0 and 1-0 or for 0-1 and 1-1.  Formats                     ENUMERATED {formats 0-0-And- 1-0,formats0-1-And-1-1},    ...   }

Based on the configuration information, the base station may configureone or a plurality of search space sets for the terminal. According toone embodiment, the base station may configure the search space set 1and the search space set 2, configure the terminal to monitor the DCIformat A scrambled with X-RNTI in the search space set 1 in the commonsearch space, and configure the terminal to monitor the DCI format Bscrambled with Y-RNTI in the search space set 2 in the terminal-specificsearch space.

According to the configuration information, one or a plurality of setsof search spaces may exist in a common search space or aterminal-specific search space. For example, search space set #1 andsearch space set #2 may be configured as a common search space, andsearch space set #3 and search space set #4 may be configured as aterminal-specific search space.

In the common search space, the combination of the following DCI formatand RNTI may be monitored. Of course, it is not limited to the followingexamples.

-   -   DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI,        SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI    -   DCI format 2_0 with CRC scrambled by SFI-RNTI    -   DCI format 2_1 with CRC scrambled by INT-RNTI    -   DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI,        TPC-PUCCH-RNTI    -   DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

In the terminal-specific search space, the combination of the followingDCI format and RNTI may be monitored. Of course, it is not limited tothe following examples.

-   -   DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI,        TC-RNTI    -   DCI format 1_0/1_1 with CRC scrambled by C-RNTI. CS-RNTI,        TC-RNTI

The specified RNTIs may follow the definitions and uses below.

C-RNTI (Cell RNTI): Terminal-specific PDSCH scheduling purpose.

TC-RNTI (Temporary Cell RNTI): Terminal-specific PDSCH schedulingpurpose.

CS-RNTI (Configured Scheduling RNTI): Semi-statically configuredterminal-specific PDSCH scheduling purpose.

RA-RNTI (Random Access RNTI): PDSCH scheduling in random access stage.

P-RNTI (Paging RNTI): PDSCH scheduling for paging transmission.

SI-RNTI (System information RNTI): For PDSCH scheduling where systeminformation is transmitted.

INT-RNTI (Interruption RNTI): Used to inform whether or not the PDSCH ispuncturing.

TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Purpose ofindicating power control command for PUSCH.

TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Purpose ofindicating power control command for PUCCH.

TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Purpose ofindicating power control command for SRS.

In an embodiment, the DCI formats described above may be defined as in[Table 10] below.

TABLE 10 DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slotformat 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol (s)where UE may assume no transmissionis intended for the UE 2_2Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of agroup of TPC commands for SRS transmissions by one or more UEs

According to an embodiment, in 5G, a plurality of search space sets maybe configured with different parameters (e.g., parameters in [Table 8]).Therefore, the set of search space sets monitored by the terminal ateach point in time may be different. For example, if the search spaceset #1 is configured for the X-slot period, the search space set #2 isconfigured for the Y-slot period, and X and Y are different, theterminal may monitor both the search space set #1 and the search spaceset #2 in a specific slot, and monitor one of the search space set #1and the search space set #2 in a specific slot.

When a plurality of search space sets are configured for the terminal,the following conditions may be considered in order to determine the setof search spaces that the terminal should monitor.

[Condition 1: Limit the Maximum Number of PDCCH Candidates]

The number of PDCCH candidates that may be monitored per slot may notexceed M^(μ). M^(μ) may be defined as the maximum number of PDCCHcandidate groups per slot in a cell configured to a subcarrier spacingof 15·2μ kHz, and may be defined as shown in [Table 11] below.

TABLE 11 Maximum number of PDCCH candidates per slot and per μ servingcell (M^(μ)) 0 44 1 36 2 22 3 20

[Condition 2: Limit the Maximum Number of CCEs]

The number of CCEs constituting the entire search space per slot (here,the entire search space may mean the entire set of CCEs corresponding toa union area of a plurality of search space sets) may not exceed C^(μ).C^(μ) may be defined as the maximum number of CCEs per slot in a cellconfigured to a subcarrier spacing of 15·2^(μ) kHz, and may be definedas shown in [Table 12] below.

TABLE 12 Maximum number of CCEs per slot and per μ serving cell (C^(μ))0 56 1 56 2 48 3 32

For the convenience of description, a situation that satisfies both ofthe conditions 1 and 2 at a specific point in time may be exemplarilydefined as “condition A”. Therefore, not satisfying the condition A maymean not satisfying at least one of the conditions 1 and 2 describedabove.

Depending on the configurations of the search space sets of the basestation, a condition A may not be satisfied at a specific time. If thecondition A is not satisfied at a specific time, the terminal may selectand monitor only a subset of the set of search spaces configured tosatisfy the condition A at the time, and the base station may transmitthe PDCCH to the selected search space set.

According to an embodiment, the following method may be followed as amethod of selecting some search spaces from a set of all set searchspaces.

[Method 1]

If the condition A for the PDCCH is not satisfied at a specific time(slot), the terminal (or the base station) may preferentially select aset of search spaces in which the search space type is configured as acommon search space from among the set of search spaces existing at acorresponding time point over the set of search spaces configured as aterminal-specific search space.

When all of the set of search spaces configured as a common search spaceare selected (i.e., when the condition A is satisfied even afterselecting all search spaces set as a common search space), the terminal(or the base station) may select a set of search spaces configured as aterminal-specific search space. At this time, when there are a pluralityof search space sets configured as terminal-specific search spaces, asearch space set having a low search space set index may have a higherpriority. In consideration of a priority, the terminal or the basestation may select the terminal-specific search space sets within arange in which condition A is satisfied.

In the following, time and frequency resource allocation methods fordata transmission in NR are described.

In NR, the following detailed frequency domain resource allocation(FD-RA) may be provided in addition to frequency axis resource candidateallocation through BWP indication. FIG. 6 illustrates a view for anexample of PDSCH frequency axis resource allocation in a wirelesscommunication system according to an embodiment.

Specifically, FIG. 6 illustrates three types of frequency axis resourceallocation methods of type 0 (6-00), type 1 (6-05), and dynamic switch(6-10) configurable through an upper layer in NR.

Referring to FIG. 6, if the terminal is configured to use only resourcetype 0 through upper layer signaling (6-00), some downlink controlinformation (DCI) for allocating PDSCH to the corresponding terminal hasa bitmap composed of NRBG bits. The conditions for this will beexplained again later. At this time, NRBG refers to the number ofresource block groups (RBG) determined as shown in [Table 13] accordingto the BWP size allocated by the BWP indicator and the upper layerparameter RBG-Size. Data is transmitted to the RBG indicated by 1.

TABLE 13 Bandwidth Part Size Configuration 1 Configuration 2  1-36 2 437-72 4 8  73-144 8 16 145-275 16 16

If the terminal is configured to use only resource type 1 through upperlayer signaling 6-05, some DCIs allocating PDSCH to the correspondingterminal have frequency axis resource allocation information composed of┌log₂(N_(RB) ^(DL,BWP)(N_(RB) ^(DL,BWP)+1)/2┐ bits. The conditions forthis will be explained again later. Through this, the base station mayconfigure a starting VRB 6-20 and a length 6-25 of frequency axisresources that are continuously allocated therefrom.

If the terminal is configured to use both resource type 0 and resourcetype 1 through upper layer signaling (6-10), some DCIs allocating PDSCHto the corresponding terminal have frequency axis resource allocationinformation composed of bits of a larger value 6-35 among payload 6-15for configuring resource type 0 and payload 6-20, 6-25 for configuringresource type 1. The conditions for this will be explained again later.At this time, one bit may be added to the first part (MSB) of thefrequency axis resource allocation information in DCI, and when thecorresponding bit is 0, the one bit may indicate that resource type 0 isused, and when the corresponding bit is 1, the one bit may indicate thatresource type 1 is used.

In the following, a time domain resource allocation method for a datachannel in a next generation mobile communication system (5G or NRsystem) is described.

The base station may configure a table of time domain resourceallocation information for a downlink data channel (physical downlinkshared channel (PDSCH)) and an uplink data channel (physical uplinkshared channel PUSCH)) to the terminal as higher layer signaling (e.g.,RRC signaling). A table consisting of a maximum ofmaxNrofDL−Allocations=16 entries may be configured for PDSCH, and atable consisting of a maximum of maxNrofUL-Allocations=16 entries may beconfigured for PUSCH. In an embodiment, in the time domain resourceallocation information, PDCCH-to-PDSCH slot timing (corresponding to atime spacing in slot units between the time when the PDCCH is receivedand the time when the PDSCH scheduled by the received PDCCH istransmitted, denoted by K0), PDCCH-to-PUSCH slot timing (correspondingto the time interval in slot units between the time when the PDCCH isreceived and the time when the received PDCCH schedules the PUSCH istransmitted, denoted by K2), information about the location and lengthof a start symbol for which PDSCH or PUSCH is scheduled in the slot, amapping type of PDSCH or PUSCH, and the like may be included. Forexample, information such as [Table 14] or [Table 15] below may benotified of from the base station to the terminal.

TABLE 14 PDSCH-TimeDomainResourceAllocationList information elementPDSCH-TimeDomainResourceAllocationList  ::=SEQUENCE (SIZE(1..maxNrofDL-Allocations)) PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation  ::=SEQUENCE {  k0 INTEGER (0..OPTIONAL, -- Need S    (PDCCH-to-PDSCH timing, slot unit)   mappingTypeENUMERATED {typeA, typeB},   (PDSCH mapping type)   startSymbolAndLength INTEGER (0 .. 127)   (start symbol and length of PDSCH)

TABLE 15 PUSCH-TimeDomainResourceAllocationList information elementPUSCH-TimeDomainResourceAllocationList  ::=SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::=SEQUENCE {  K2 INTEGER (0..32)OPTIONAL, -- Need S    (PDCCH-to-PUSCH timing, slot unit)   mappingType ENUMERATED {typeA, typeB},   (PUSCH mapping type)  startSymbolAndLength   INTEGER (0.. 127)   (start symbol and length ofPUSCH)

The base station may notify the terminal of one of the entries in thetable for the time domain resource allocation information describedabove through L1 signaling (e.g., DCI) (e.g., indicated by the ‘timedomain resource allocation’ field in DCI). The terminal may acquire timedomain resource allocation information for PDSCH or PUSCH based on theDCI received from the base station.

FIG. 7 illustrates a view for an example of time-axis resourceallocation of PDSCH in a wireless communication system according to anembodiment.

Referring to FIG. 7, a base station may indicate subcarrier spacings(SCS) (μ_(PDSCH), μ_(PDCCH)) of a data channel and a control channelconfigured using an upper layer, scheduling offset (K0) value, and thetime axis position of the PDSCH resource according to the OFDM symbolstart position (7-00) and length (7-05) in one slot dynamicallyindicated through DCI.

FIG. 8 illustrates a view for an example of time axis resourceallocation according to subcarrier spacings of a data channel and acontrol channel in a wireless communication system according to anembodiment.

Referring to FIG. 8, it may be seen that when the subcarrier spacings ofthe data channel and the control channel are the same (8-00,μ_(PDSCH)=μ_(PDCCH)), the slot number for data and control is the same,so that a scheduling offset occurs for the base station and the terminalaccording to a predetermined slot offset K0 in the base station andterminal. On the other hand, it may be seen that when the subcarrierspacings of the data channel and the control channel are different(8-05, μ_(PDSCH)≠μ_(PDCCH)), the slot numbers for data and control aredifferent, so that a scheduling offset occurs for the base station andthe terminal, based on the subcarrier spacing of the PDCCH, according toa predetermined slot offset K₀ in the base station and terminal.

In LTE and NR, the terminal has a procedure of reporting the capabilitysupported by the terminal to the corresponding base station whileconnected to the serving base station. In the following description,this is referred to as terminal (UE) capability (reporting).

The base station may transfer a terminal capability enquiry messagerequesting capability reporting to a terminal in a connected state. Inthe message, the base station may include a request for terminalcapability for each RAT type. The request for each RAT type may includerequested frequency band information. In addition, the terminalcapability enquiry message may request a plurality of RAT types from oneRRC message container, or a terminal capability enquiry messageincluding a request for each RAT type may be transferred to the terminalmultiple times. That is, the terminal capability enquiry may be repeatedmultiple times, and the terminal may report the number of times byconfiguring the corresponding terminal capability information message.In the next-generation mobile communication system, the terminalcapability requests for MR-DC including NR, LTE, and E-UTRA New radiodual connectivity (EN-DC) may be made. In addition, the terminalcapability enquiry message is generally transmitted initially after theterminal is connected to the base station, but may be requested underany conditions when the base station needs.

In the step, the terminal receiving the terminal capability reportrequest from the base station may configure the terminal capabilityaccording to the RAT type and band information requested from the basestation. A Method of configuring terminal capability by the terminal inthe NR system is as follows.

1. If the terminal is provided with a list of LTE and/or NR bands at theterminal capability request from the base station, the terminal mayconfigure a band combination (BC) for EN-DC and NR stand-alone (SA).That is, a candidate list of BC for EN-DC and NR SA may be configuredbased on bands requested by the FreqBandList to the base station. Also,the priority of the bands has priority in the order described inFreqBandList.

2. If the base station requests the terminal capability report byconfiguring the “eutra-nr-only” flag or the “eutra” flag, the terminalmay completely remove the NR SA BCs from the configured BC candidatelist. This operation may be performed only when the LTE base station(eNB) requests “eutra” capability.

3. Thereafter, the terminal may remove fallback BCs from the candidatelist of BCs configured in the above step. Here, fallback BC correspondsto a case in which a band corresponding to at least one SCell is removedfrom a super set BC, and may be omitted because the super set BC mayalready cover the fallback BC. This step is also applied to Multi-RATDual Connectivity (MR-DC), that is, LTE bands may also be applied. Theremaining BC after this stage is the final “candidate BC list”.

4. The terminal may select BCs to report by selecting BCs correspondingto the requested RAT type in the final “candidate BC list”. In thisstep, the terminal may configure the supportedBandCombinationList in apredetermined order. That is, the terminal may configure BC and terminalcapabilities to report in a predetermined order of rat-Type.(nr→eutra-nr→eutra). In addition, the featureSetCombination for theconfigured supportedBandCombinationList may be configured, and the listof “candidate feature set combinations” may be constructed from thecandidate BC list where the list for fallback BC (which includes thesame or lower level capability) is removed. The “candidate feature setcombination” includes both feature set combinations for NR and EUTRA-NRBC, and may be obtained from feature set combinations ofUE-NR-Capabilities and UE-MRDC-Capabilities containers.

5. Further, if the requested rat type is eutra-nr,featureSetCombinations may be included in both containers,UE-MRDC-Capabilities and UE-NR-Capabilities. However, the feature set ofNew Radio (NR) may include only UE-NR-Capabilities.

After the terminal capability is configured, the terminal may transmit aterminal capability information message including terminal capability tothe base station. The base station may then perform appropriatescheduling and transmission/reception management for the correspondingterminal, based on the terminal capability received from the terminal.

In the NR, the terminal may transmit uplink control information (UCI) tothe base station through a physical uplink control channel (PUCCH). Thecontrol information may include at least one of a HARQ-ACK indicatingwhether demodulation/decryption is successful for a transport block (TB)received by the terminal through the PDSCH, a scheduling request (SR)for requesting resource allocation to a PUSCH base station for uplinkdata transmission by the terminal, and channel state information (CSI),which is information for reporting the channel state of the terminal.

The PUCCH resource may be largely classified into a long PUCCH and ashort PUCCH according to the allocated symbol length. In NR, a longPUCCH has a length of 4 symbols or more in a slot, and a short PUCCH hasa length of 2 symbols or less in a slot.

Describing the Long PUCCH in more detail, the long PUCCH may be used forthe purpose of improving uplink cell coverage, and thus may betransmitted in the DFT-S-OFDM method, which is a short carriertransmission rather than OFDM transmission. The long PUCCH supportstransport formats such as PUCCH format 1, PUCCH format 3, and PUCCHformat 4 depending on the number of control information bits that can besupported and whether terminal multiplexing is supported through Pre-DFTOCC support at the front end of IFFT.

First, PUCCH format 1 is a long PUCCH format, based on DFT-S-OFDM thatcan support up to 2 bits of control information and uses frequencyresources of 1 RB. The control information may be composed of HARQ-ACK,SR or a combination thereof. In PUCCH format 1, an OFDM symbol includinga demodulation reference signal (DMRS), which is a demodulationreference signal (or reference signal), and an OFDM symbol including aUCI are repeatedly configured.

For example, when the number of transmission symbols in PUCCH format 1is 8 symbols, the first start symbol of 8 symbols is sequentiallycomposed of DMRS symbols, UCI symbols, DMRS symbols, UCI symbols, DMRSsymbols, UCI symbols, DMRS symbols, and UCI symbols. The DMRS symbol isspread by using an orthogonal code (or orthogonal sequence or spreadingcode, w_i(m)) in a time axis in a sequence corresponding to a length of1 RB on a frequency axis within one OFDM symbol, and is transmittedafter performing IFFT.

The UCI symbol has a structure that generates d(0) by modulating 1-bitcontrol information by BPSK and 2-bit control information by QPSK,scrambles and multiplies the generated d(0) by a sequence correspondingto the length of 1 RB on the frequency axis, spreads the scrambledsequence using an orthogonal code (or orthogonal sequence or spreadingcode, w_i(m)) on the time axis, and transmits the same after performingIFFT.

The terminal generates a sequence, based on the group hopping orsequence hopping configuration and the configured ID, received from thebase station as a higher signal, and generates a sequence correspondingto a length of 1 RB by cyclic shifting the generated sequence with aninitial cyclic shift (CS) value set as a higher signal to.

w_i(m) is determined as given like

${w_{i}(m)} = e^{\frac{j\; 2{{\pi\phi}{(m)}}}{N_{SF}}}$when the length of the spreading code (NSF) is given, and is given as inTable 16 below. i means the index of the spreading code itself, and mmeans the index of elements of the spreading code. Here, the numbers in[ ] in [Table 16] mean ϕ(m), for example, when the length of thespreading code is 2 and the index i=0 of the configured spreading code,the spreading code w_i(m) becomes

w_(i)(0) = e^(j 2π ⋅ 0/N_(SF)) = 1, w_(i)(1) = e^(j 2π ⋅ 0/N_(SF)),so that w_i(m)=[1 1].

TABLE 16 Spreading code for PUCCH format 1 wi(m) = e^(j2πφ(m)/N) ^(SF)φ(m) N_(SF) i = 0 i = 1 i = 2 i = 3 i = 4 i = 5 i = 6 1 [0] — — — — — —2 [0 0] [0 1] — — — — — 3 [0 0 0] [0 1 2] [0 2 1] — — — — 4 [0 0 0 0] [02 0 2] [0 0 2 2 ] [0 2 2 0] — — — 5 [0 0 0 0 0 ] [0 1 2 3 4] [0 2 4 1 3][0 3 1 4 2] [0 4 3 2 1] — — 6 [0 0 0 0 0 0] [0 1 2 3 4 5] [0 2 4 0 2 4][0 3 0 3 0 3] [0 4 2 0 4 2] [0 5 4 3 2 1] — 7 [0 0 0 0 0 0 0] [0 1 2 3 45 6] [0 2 4 6 1 3 5] [0 3 6 2 5 1 4] [0 4 1 5 2 6 3] [0 5 3 1 6 4 2] [06 5 4 3 2 1]

Next, PUCCH format 3 is a long PUCCH format, based on DFT-S-OFDM thatcan support control information of more than 2 bits, and the number ofRBs used may be configured through an upper layer. The controlinformation may be composed of HARQ-ACK, SR, CSI or a combinationthereof. The DMRS symbol positions in PUCCH format 3 are presented inthe following [Table 17] depending on whether frequency hopping in theslot and additional DMRS symbols are configured.

TABLE 17 DMRS position in PUCCH format 3/4 Additional DMRS is notAdditional DMRS is configured configured PUCCH Frequency Frequencyformat 3/4 hopping is Frequency hopping is Frequency Transmission nothopping is not hopping is length configured configured configuredconfigured  4 1 0, 2 1 0, 2  5 0, 3 0, 3  6 1, 4 1, 4  7 1, 4 1, 4  8 1,5 1, 5  9 1, 6 1, 6 10 2, 7 1, 3, 6, 8 11 2, 7 1, 3, 6, 9 12 2, 8 1, 4,7, 10 13 2, 9 1, 4, 7, 11 14 3, 10 1, 5, 8, 12

For example, if the number of transmission symbols in PUCCH format 3 is8 symbols, the first start symbol of 8 symbols starts with 0, and DMRSis transmitted to the 1st and 5th symbols. The above table also appliesto the DMRS symbol position in PUCCH format 4.

Next, PUCCH format 4 is a long PUCCH format based on DFT-S-OFDM capableof supporting more than 2 bits of control information, and usesfrequency resources of 1 RB. The control information may be composed ofHARQ-ACK, SR, CSI, or a combination thereof. The difference betweenPUCCH format 4 and PUCCH format 3 is that PUCCH format 4 may multiplexPUCCH format 4 of multiple terminals within one RB. It is possible tomultiplex PUCCH format 4 of multiple UEs by applying Pre-DFT OCC tocontrol information in the IFFT front end. However, the number ofcontrol information symbols that may be transmitted by one terminal isreduced according to the number of terminals to be multiplexed. Thenumber of multiplexable terminals, that is, the number of different OCCsthat may be used may be 2 or 4, and the number of OCCs and the OCC indexto be applied may be configured through an upper layer.

Next, the short PUCCH will be described. The short PUCCH may betransmitted in both a downlink centric slot (downlink centric slot) andan uplink centric slot (uplink centric slot), and is usually transmittedin the last symbol of the slot, or the OFDM symbol at the back (e.g.,the last OFDM symbol or the second OFDM symbol at the end, or the last 2OFDM symbols). Of course, it is also possible to transmit the ShortPUCCH at an arbitrary position in the slot. Also, the short PUCCH may betransmitted using one OFDM symbol or two OFDM symbols. The short PUCCHmay be used to shorten a delay time compared to long PUCCH in asituation in which uplink cell coverage is good and is transmitted inCP-OFDM.

The short PUCCH supports transmission formats such as PUCCH format 0 andPUCCH format 2 according to the number of control information bits thatcan be supported. First, PUCCH format 0 is a short PUCCH format capableof supporting up to 2 bits of control information, and uses frequencyresources of 1 RB. The control information may be composed of HARQ-ACK,SR or a combination thereof. The PUCCH format 0 does not transmit DMRS,and has a structure in which only sequences mapped to 12 subcarriers ona frequency axis within one OFDM symbol are transmitted. The terminalgenerates a sequence based on the group hopping or sequence hopping setand the set ID received as a higher signal from the base station,cyclically shifts the generated sequence to a final CS value obtained byadding another CS value according to whether the indicated initialcyclic shift (CS) value is ACK or NACK, and then maps and transmits themapped sequence to 12 subcarriers.

For example, if HARQ-ACK is 1 bit, as shown in [Table 18] below, 6 isadded to the initial CS value to generate the final CS, and in the caseof NACK, 0 is added to the initial CS to generate the final CS. The CSvalue 0 for NACK and the CS value 6 for ACK are defined in the standard,and the terminal always generates PUCCH format 0 according to the valueand transmits 1-bit HARQ-ACK.

TABLE 18 1 bit HARQ-ACK NACK ACK Final CS (Initial CS + 0) (Initial CS +6) MOD 12 = Initial CS MOD 12

For example, in a case where HARQ-ACK is 2 bits, as shown in [Table 19],if 2-bit HARQ-ACK is (NACK, NACK), 0 is added to the initial CS value,if 2-bit HARQ-ACK is (NACK, ACK), 3 is added to the initial CS value, if2-bit HARQ-ACK is (ACK, ACK), 6 is added to the initial CS value, and if2-bit HARQ-ACK is (ACK, NACK), 9 is added to the initial CS value. TheCS values for (NACK, NACK) 0, CS values for (NACK, ACK) 3, CS values for(ACK, ACK) 6, and CS values for (ACK, NACK) 9 are defined in thespecification, and the terminal always generates a PUCCH format 0according to the above values and transmits a 2-bit HARQ-ACK.

When the final CS value exceeds 12 by the CS value added according toACK or NACK to the initial CS value, since the length of the sequence is12, modulo 12 is applied to the final CS value.

TABLE 19 2 bit HARQ-ACK NACK, NACK NACK, ACK ACK, ACK ACK, NACK Final CS(Initial CS + 0) (Initial CS + 3) (Initial CS + 6) (Initial CS + 9) MOD12 = Initial CS MOD 12 MOD 12 MOD 12

Next, PUCCH format 2 is a short PUCCH format supporting more than 2 bitsof control information, and the number of RBs used may be configuredthrough an upper layer. The control information may be composed ofHARQ-ACK, SR, CSI, or a combination thereof. In the PUCCH format 2, whenthe index of the first subcarrier is #0, the position of the subcarrierthrough which the DMRS is transmitted in one OFDM symbol is fixed to asubcarrier having an index of #1, #4, #7, #10. The control informationis mapped to the remaining subcarriers except for the subcarrier wherethe DMRS is located through a modulation process after channel coding.

In summary, the values and ranges that may be configured for each PUCCHformat described above may be summarized as in [Table 20]. If there isno need to configure a value in the following table, the value isindicated as N.A.

TABLE 20 PUCCH PUCCH PUCCH PUCCH PUCCH Format 0 Format 1 Format 2 Format3 Format 4 Starting Configurability ✓ ✓ ✓ ✓ ✓ symbol Value range 0-130-10 0-13 0-10 0-10 Number of Configurability ✓ ✓ ✓ ✓ ✓ symbols in Valuerange 1, 2 4-14 1, 2 4-14 4-14 a slot Index for Configurability ✓ ✓ ✓ ✓✓ identifying Value range 0-274 0-274 0-274 0-274 0-274 starting PRBNumber of Configurability N.A. N.A. ✓ ✓ N.A. PRBs Value range N.A. N.A.1-16 1-6, 8-10, N.A. (Default is 1) (Default is 1) 12, 15, 16 (Defaultis 1) Enabling Configurability ✓ ✓ ✓ ✓ ✓ frequency Value range On/OffOn/Off On/Off On/Off On/Off hopping (only for 2 (only for 2 (intra-slot)symbol) symbol) Freq.cy Configurability ✓ ✓ ✓ ✓ ✓ resource of Valuerange 0-274 0-274 0-274 0-274 0-274 2^(nd) hop if intra-slot frequencyhopping is enabled Index of Configurability ✓ ✓ N.A. N.A. N.A. initialcyclic Value range 0-11 0-11 N.A. N.A. N.A. shift Index ofConfigurability N.A. ✓ N.A. N.A. N.A. time-domain Value range N.A. N.A.N.A. N.A. OCC Length of Configurability N.A. N.A. N.A. N.A. ✓ Pre-DFTValue range N.A. N.A. N.A. N.A. 2, 4 OCC Index of Configurability N.A.N.A. N.A. N.A. ✓ Pre-DFT Value range N.A. N.A. N.A. N.A. 0, 1, 2, 3 OCC

Meanwhile, in order to improve uplink coverage, multi-slot repetitionmay be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition maybe configured for each PUCCH format.

Next, the PUCCH resource configuration of the base station or theterminal will be described. The base station may configure PUCCHresources for each BWP through an upper layer for a specific terminal.The configuration may be as shown in [Table 21].

TABLE 21 PUCCH-Config ::=   SEQUENCE {  resourceSetToAddModList  SEQUENCE (SIZE (1..maxNrofPUCCH- ResourceSets)) OFPUCCH-ResourceSet OPTIONAL, - - Need N resourceSetToReleaseList  SEQUENCE (SIZE (1..maxNrofPUCCH- ResourceSets)) OFPUCCH-ResourceSetId  OPTIONAL, - - Need N resourceToAddModList  SEQUENCE (SIZE (1..maxNrofPUCCH- Resources)) OF PUCCH-Resource OPTIONAL, - - Need N resourceToReleaseList   SEQUENCE (SIZE(1..maxNrofPUCCH- Resources)) OF PUCCH-ResourceId  OPTIONAL, - - Need N format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL,  - - Need M format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL,  - - Need M format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL,  - - Need M format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL,  - - Need MschedulingRequestResourceToAddModList   SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig OPTIONAL,  - - Need NschedulingRequestResourceToReleaseList   SEQUENCE (SIZE (1..maxNrofSR-Resources)) (OF SchedulingRequestResourceId OPTIONAL,  - - Need M multi-CSI-PUCCH-ResourceList  SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId      OPTIONAL, - - Need M  dl-DataToUL-ACK  SEQUENCE (SIZE(1..8)) OF INTEGER (0..15)     OPTIONAL, - - Need M spatialRelationInfoToAddModList     SEQUENCE (SIZE(1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo OPTIONAL, - - Need N  spatialRelationInfoToReleaseList     SEQUENCE (SIZE(1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoIdOPTIONAL,  - - Need M pucch-PowerControl    PUCCH-PowerControl OPTIONAL, - - Need M  . . . }

According to the above table, one or more PUCCH resource sets in a PUCCHresource set for a specific BWP may be configured, and a maximum payloadvalue for UCI transmission may be configured in some of the PUCCHresource sets. Each PUCCH resource set may include one or more PUCCHresources, and each of the PUCCH resources may belong to one of thePUCCH formats described above.

For the PUCCH resource set, the maximum payload value of the first PUCCHresource set may be fixed to 2 bits, and thus the corresponding valuemay not be separately configured through an upper layer or the like.When the remaining PUCCH resource set is configured, the index of thecorresponding PUCCH resource set may be configured in ascending orderaccording to the maximum payload value, and the maximum payload valuemight not be configured in the last PUCCH resource set. The upper layerconfiguration for the PUCCH resource set may be as shown in [Table 22].

TABLE 22 - - A set with one or more PUCCH resources PUCCH-ResourceSet::=  SEQUENCE {   pucch-ResourceSetId   PUCCH-ResourceSetId,  resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OFPUCCH-ResourceId,   maxPayloadMinus1 INTEGER (4..256) OPTIONAL  - - NeedP }

The resourceList parameter of the table may include IDs of PUCCHresources belonging to the PUCCH resource set.

If the initial access or the PUCCH resource set is not configured, thePUCCH resource set as shown in [Table 22], which is composed of aplurality of cell specific PUCCH resources in the initial BWP, may beused. The PUCCH resource to be used for initial access in this PUCCHresource set may be indicated through SIB1.

TABLE 23 Set of PUCCH First Number of PRB offset initial CS Index formatsymbol symbols RB_(BWP) ^(offset) indexes  0 0 12  2 0 {0, 3}  1 0 12  20 {0, 4, 8}  2 0 12  2 3 (0, 4, 8}  3 1 10  4 0 {0, 6}  4 1 10  4 0 {0,3, 6, 9}  5 1 10  4 2 {0, 3, 6, 9}  6 1 10  4 4 {0, 3, 6, 9}  7 1  4 100 {0, 6}  8 1  4 10 0 {0, 3, 6, 9}  9 1  4 10 2 {0, 3, 6, 9} 10 1  4 104 {0, 3, 6, 9} 11 1  0 14 0 {0, 6} 12 1  0 14 0 {0, 3, 6, 9} 13 1  0 142 {0, 3, 6, 9} 14 1  0 14 4 {0, 3, 6, 9} 15 1  0 14 └N_(BWP) ^(size)/4┘{0, 3, 6, 9}

The maximum payload of each PUCCH resource included in the PUCCHresource set may be 2 bits in a case of PUCCH format 0 or 1, and may bedetermined by symbol length, number of PRBs, and maximum code rate forthe remaining formats. The aforementioned symbol length and number ofPRBs may be configured for each PUCCH resource, and the maximum coderate may be configured for each PUCCH format.

Next, PUCCH resource selection for UCI transmission will be described.In the case of SR transmission, PUCCH resource for the SR correspondingto the schedulingRequestID may be configured through the upper layer asshown in [Table 24]. The PUCCH resource may be a resource belonging toPUCCH format 0 or PUCCH format 1.

TABLE 24 SchedulingRequestResourceConfig ::= SEQUENCE { schedulingRequestResourceId  SchedulingRequestResourceId, schedulingRequestID SchedulingRequestId,  periodicityAndOffset CHOICE {  sym2  NULL,   sym60r7   NULL,   s11  NULL, -- Pecurs in every slot  s12  INTEGER (0..1),   s14  INTEGER (0..3),   s15  INTEGER (0..4),  s18  INTEGER (0..7),   s110  INTEGER (0..9),   s116  INTEGER (0..15),  s120  INTEGER (0..19),   s140  INTEGER (0..39),   s180  INTEGER(0..79),   s1160  INTEGER (0..159),   s1320  INTEGER (0..319),   s1640 INTEGER (0..639)  } OPTIONAL,  - - Need M  resource  PUCCH-ResourceIdOPTIONAL  - - Need M }

For the configured PUCCH resource, a transmission period and an offsetare configured through a periodicityAndOffset parameter of [Table 24].If there is uplink data to be transmitted by the terminal at a timecorresponding to the set period and offset, the corresponding PUCCHresource is transmitted, otherwise the corresponding PUCCH resourcemight not be transmitted.

In the case of CSI transmission, PUCCH resources to transmit a periodicor semi-persistent CSI report through PUCCH may be configured in thePUCCH-CSI-ResourceList parameter as shown in [Table 23]. The parametercontains a list of PUCCH resources for each BWP for a cell or MC totransmit a corresponding CSI report. The PUCCH resource may be aresource belonging to PUCCH format 2 or PUCCH format 3 or PUCCH format4.

TABLE 25   CSI-ReportConfig ::= SEQUENCE {    reportConfigId  CSI-ReportConfigId,    carrier  ServCellIndex OPTIONAL, Need S   ...   reportConfigType   CHOICE {     periodic    SEQUENCE {     reportSlotConfig      CSI-ReportPeriodicityAndOffset,     pucch-CSI-ResourceList       SEQUENCE (SIZE (1..maxNrofBWPs)) OFPUCCH-CSI-Resource     },     semiPersistentOnPUCCH     SEQUENCE {     reportSlotConfig      CSI-ReportPeriodicityAndOffset,     pucch-CSI-ResourceList       SEQUENCE (SIZE (1..maxNrofBWPs)) OFPUCCH-CSI-Resource     },  ... }

For the PUCCH resource, a transmission period and an offset areconfigured through reportSlotConfig in [Table 23].

In the case of HARQ-ACK transmission, the resource set of the PUCCHresource to be transmitted is first selected according to the payload ofthe UCI including the corresponding HARQ-ACK. That is, a PUCCH resourceset having a minimum payload not smaller than the UCI payload isselected. Next, the PUCCH resource in the PUCCH resource set may beselected through the PUCCH resource indicator (PRI) in DCI thatschedules the TB corresponding to the corresponding HARQ-ACK, and thePRI may be a PUCCH resource indicator specified in [Table 5] or [Table6]. The relationship between the PRI and the PUCCH resource selectedfrom the PUCCH resource set may be as shown in [Table 26].

TABLE 26 PUCCH resource indicator PUCCH resource ‘000’ 1^(st) PUCCHresource provided by pucch-ResourceId obtained from the 1^(st) value ofresourceList ‘001’ 2^(nd) PUCCH resource provided by pucch-ResourceIdobtained from the 2^(nd) value of resourceList ‘010’ 3^(rd) PUCCHresource provided by pucch-ResourceId obtained from the 3^(rd) value ofresourceList ‘011’ 4^(th) PUCCH resource provided by pucch-ResourceIdobtained from the 4^(th) value of resourceList ‘100’ 5^(th) PUCCHresource provided by pucch-ResourceId obtained from the 5^(th) value ofresourceList ‘101’ 6^(th) PUCCH resource provided by pucch-ResourceIdobtained from the 6^(th) value of resourceList ‘110’ 7^(th) PUCCHresource provided by pucch-ResourceId obtained from the 7^(th) value ofresourceList ‘111’ 8^(th) PUCCH resource provided by pucch-ResourceIdobtained from the 8^(th) value of resourceList

If the number of PUCCH resources in the selected PUCCH resource set isgreater than 8, PUCCH resources may be selected by the followingequation.

$\begin{matrix}{r_{PUCCH} = \begin{Bmatrix}{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lceil {R_{PUCCH}/8} \right\rceil}{N_{{CCE},p}} \right\rfloor + {\Delta_{PRI} \cdot \left\lceil \frac{R_{PUCCH}}{8} \right\rceil}} & {{{if}\mspace{14mu}\Delta_{PRI}} < {R_{PUCCH}{mod}\; 8}} \\{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lfloor {R_{PUCCH}/8} \right\rfloor}{N_{{CCE},p}} \right\rfloor + {\Delta_{PRI} \cdot \left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor} + {R_{PUCCH}{mod}\; 8}} & {{{if}\mspace{14mu}\Delta_{PRI}} \geq {R_{PUCCH}{mod}\; 8}}\end{Bmatrix}} & \left\lbrack {{Equation}\mspace{14mu} 1} \right\rbrack\end{matrix}$

In the above equation, r_(PUCCH) represents the index of the selectedPUCCH resource in the PUCCH resource set, R_(PUCCH) represents thenumber of PUCCH resources belonging to the PUCCH resource set, Δ_(PRI)represents the PRI value, N_(CCE,p) represents the total number of CCEsof the CORESET to which the reception DCI belongs, and n_(CCE,p)represents the first CCE index for the reception DCI.

The time when the corresponding PUCCH resource is transmitted is afterthe K₁ slot from the TB transmission corresponding to the correspondingHARQ-ACK. The candidates of the K₁ value are configured as an upperlayer, and more specifically, are configured in a dl-DataToUL-ACKparameter in PUCCH-Config specified in [Table 21]. The K₁ value of oneof these candidates may be selected by the PDSCH-to-HARQ feedback timingindicator in DCI scheduling the TB, and this value may be a valuespecified in [Table 5] or [Table 6]. Meanwhile, the unit of the K₁ valuemay be a slot unit or a sub-slot unit. Here, a sub-slot is a unit havinga length smaller than that of a slot, and one or a plurality of symbolsmay constitute one sub-slot.

Next, a case in which two or more PUCCH resources are located in oneslot will be described. The terminal may transmit UCI through one or twoPUCCH resources in one slot or sub-slot, when UCI is transmitted throughtwo PUCCH resources in one slot/sub-slot, i) each PUCCH resource doesnot overlap in a symbol unit, and ii) at least one PUCCH resource may bea short PUCCH. Meanwhile, the terminal might not expect to transmit aplurality of PUCCH resources for HARQ-ACK transmission in one slot.

Next, a PUCCH transmission procedure when two or more PUCCH resourcesoverlap will be described. When two or more PUCCH resources overlap, oneof the overlapping PUCCH resources may be selected or a new PUCCHresource may be selected according to the above-described condition,that is, the transmitted PUCCH resource should not overlap in a symbolunit. In addition, all UCI payloads transmitted through overlappingPUCCH resources may be multiplexed or partially dropped. First, case 1:multi-slot repetition is not configured in the PUCCH resource, and case2: the multi-slot repetition is configured will be described.

For Case 1, when the PUCCH resource overlaps, Case 1 is divided intoCase 1-1) when two or more PUCCH resources for HARQ-ACK transmissionoverlap and Case 1-2) for the rest. Case 1-1) is illustrated in FIG. 9.

FIG. 9 illustrates a view for a case in which multiple PUCCH resourcesfor HARQ-ACK transmission for a PDSCH overlap when multi-slot repetitionis not configured according to an embodiment. Referring to FIG. 9, fortwo or more different PDCCHs (9-10, 9-11) that schedule the PDSCH, whenthe transmission slots of the PUCCH resource corresponding to each PDCCHare the same, the corresponding PUCCH resources may be considered tooverlap each other. That is, when the uplink slots corresponding to theK₁ value (9-50, 9-51) indicated by multiple PDCCHs are the same, PUCCHresources corresponding to the corresponding PDCCHs may be considered tooverlap with each other.

At this time, among the PUCCH resources indicated by the PRIs 9-40, 9-41in the PDCCH, only the PUCCH resource 9-31 selected based on the PRI9-41 corresponding to the PDCCH 9-11 transmitted at the last time isselected and transmitted. Therefore, all of the HARQ-ACK information forPDSCH 9-21 through the selected PUCCH resource 9-31, and the HARQ-ACKinformation for other PUCCH 9-30 overlapping the PUCCH resource 9-31 aretransmitted after being encoded by a predefined HARQ-ACK codebook.

Next, the case 1-2) in which the PUCCH resource for HARQ-ACKtransmission and the PUCCH resource for SR and/or CSI transmissionoverlap, or when a plurality of PUCCH resources for SR and/or CSItransmission overlap will be described. In the above case, when aplurality of PUCCH resources transmitted in the same slot overlap one ormore symbols on the time axis, the corresponding PUCCH resources aredefined to overlap, and whether to multiplex UCIs in these resources maybe summarized as in [Table 27].

TABLE 27 PUCCH 1 PUCCH 2 SR HARQ-ACK CSI SR — Case 1-2-1 Always(Multiplex or not multiplex depending on PUCCH format) HARQ-ACK Alwaysmultiplex Case 1-2-2 (HARQ-ACK (Multiplex or not codebook) by higherlager) CSI Always Case 1-2-2 Case 1-2-2 multiplex

According to the above table, these UCIs are always multiplexed whenoverlapping between PUCCH resources where HARQ-ACK is transmitted oroverlapping between PUCCHs where SR and CSI are transmitted.

On the other hand, when each PUCCH resource in which SR and HARQ-ACK aretransmitted overlaps, that is, in case 1-2-1, whether to perform UCImultiplexing is divided according to the format of the PUCCH resource.

-   -   SR on PUCCH format 0+HARQ-ACK on PUCCH format 1: SR is dropped        and only HARQ-ACK is transmitted    -   Other cases: SR and HARQ-ACK are multiplexed

In addition, in the remaining cases corresponding to Case 1-2-2, thatis, when HARQ-ACK and CSI overlap between transmitted PUCCH resources orwhen CSI overlaps among multiple transmitted PUCCH resources, whetherthese UCIs are multiplexed may follow the upper layer configuration. Inaddition, configuration of whether to multiplex between HARQ-ACK and CSIand configuration of whether to multiplex between multiple CSIs may beindependently performed.

For example, whether to multiplex between HARQ-ACK and CSI may beconfigured through simultaneousHARQ-ACK-CSI parameters per PUCCH format2, 3, or 4, and the corresponding parameters may be configured as thesame value for the PUCCH format. If multiplexing is configured not to beperformed through the above parameters, only HARQ-ACK may be transmittedand overlapping CSI may be dropped. In addition, whether to multiplexbetween multiple CSIs may be configured through amulti-CSI-PUCCH-ResourceList parameter in PUCCH-Config. That is, whenthe multi-CSI-PUCCH-ResourceList parameter is configured, multiplexingbetween CSIs may be performed, otherwise, only the PUCCH correspondingto the CSI having a higher priority may be transmitted according to thepriority between CSIs.

When the UCI multiplexing is performed as described above, the method ofselecting the PUCCH resource to transmit the corresponding UCI resourceand the multiplexing method may vary according to the information of theoverlapped UCI and the format of the PUCCH resource, which may besummarized as in [Table 28].

TABLE 28 HARQ-ACK SR Format CSI PUCCH 2 PUCCH 1 (format 0/1) Format 10/2/3/4 (format 2/3/4) SR — Option 1 Option 2 Option 3 (format 0/1)HARQ-ACK Format 1 Option 1 Option 4 Option 4 Option 5 (grant-based)Option 6 (SPS) Format Option 2 Option 4 Option 4 Option 5 0/2/3/4(grant-based) Option 6 (SPS) CSI Option 3 Option 5 Option 5 Option 7(format 2/3/4) (grant-based) (grant-based) Option 6 (SPS) Option 6 (SR3)

Each option in the above table is as follows.

-   -   Option 1: Depending on the SR value of the SR PUCCH resource        overlapped with the HARQ-ACK PUCCH resource, the PUCCH resource        selection is different. That is, if the SR value is positive,        the PUCCH resource for SR is selected, and if the SR value is        negative, the PUCCH resource for HARQ-ACK is selected. HARQ-ACK        information is transmitted to the selected PUCCH resource.    -   Option 2: The HARQ-ACK information and SR information is        multiplexed and transmitted to PUCCH resource for HARQ-ACK.    -   Option 3: The SR information and HARQ-ACK information is        multiplexed and transmitted to the PUCCH resource for CSI.    -   Option 4: The PUCCH resource for overlapping HARQ-ACK is        transmitted. —Detailed operations are described in case 1-1)        above.    -   Option 5: When the PUCCH resource for HARQ-ACK corresponding to        PDSCH scheduled as PDCCH and the PUCCH resource for CSI        transmission overlap and multiplexing between HARQ-ACK and CSI        is configured as an upper layer, the PUCCH resource for HARQ-ACK        information and the CSI information are multiplexed and        transmitted.    -   Option 6: When the PUCCH resource for HARQ-ACK corresponding to        semi-persistent scheduling (SPS) PDSCH and the PUCCH resource        for CSI transmission overlap and multiplexing between HARQ-ACK        and CSI is configured as a higher layer, the HARQ-ACK        information and the CSI information are multiplexed and        transmitted to the PUCCH resource for HARQ-ACK.

If the PUCCH resource list for multiplexing to the upper layer, that is,the multi-CSI-PUCCH-ResourceList is configured, all of the multiplexedUCI payloads among the resources in the list may be transmitted, and theUCI payload is transmitted after selecting one resource having thelowest index. If there is no resource that may transmit all of themultiplexed UCI payloads in the list, the resource with the largestindex is selected and HARQ-ACK and CSI reports corresponding to thenumber of transmittable resources are transmitted.

-   -   Option 7: When multiple PUCCH resources for CSI transmission        overlap and multiplexing between multiple CSIs is configured as        the upper layer, the PUCCH resource list for CSI multiplexing        configured as the upper layer, that is, multiplexed in the        multi-CSI-PUCCH-ResourceList All UCI payloads may be transmitted        and the UCI payload is transmitted after selecting the resource        with the lowest index. If there is no resource that may transmit        all of the multiplexed UCI payloads in the list, the resource        with the largest index is selected and CSI reports corresponding        to the number of transmittable resources are transmitted.

In the above, for the convenience of description, the case where twoPUCCH resources overlap is focused upon, but the method may be similarlyapplied even when three or more PUCCH resources overlap. For example,when the PUCCH resource multiplexed with SR+HARQ-ACK overlaps with theCSI PUCCH resource, a multiplexing method between HARQ-ACK and CSI maybe followed.

If the transmission is configured without multiplexing between specificUCIs, according to the order of HARQ-ACK>SR>CSI, a UCI with a higherpriority may be transmitted and a UCI with a lower priority may bedropped. If the transmission is configured without multiplexing whenmultiple CSI PUCCH resources overlap, PUCCH corresponding to a CSIhaving a higher priority may be transmitted, and PUCCH corresponding toanother CSI may be dropped.

Next, Case 2, that is, when multi-slot repetition is configured, isdivided into Case 2-1) when two or more PUCCH resources for HARQ-ACKtransmission are located in the same start slot and Case 2-2) for therest. Each case is shown in FIG. 10.

FIG. 10 illustrates a view for a case where PUCCH resources overlap whenmulti-slot repetition is configured according to an embodiment.

Referring to Case 2-1), when multi-slot repetition is configured in aPUCCH resource for HARQ-ACK, that is, PUCCH #1 is repeatedly transmittedover multiple slots (10-30, 10-40) and PUCCH #2 is also repeatedlytransmitted over multiple slots (10-31, 10-41), if the starting slots ofthe two PUCCH indicated by K₁ are the same, a single PUCCH resource(PUCCH transmitted at the last time point in one slot), that is, PUCCH#2 may be selected in the same manner as in Case 1-1). Accordingly,HARQ-ACKs corresponding to PDSCH #1 and PDSCH #2 are multiplexed andtransmitted to the corresponding PUCCH through the HARQ-ACK codebook.

For the convenience of description, the case where a plurality ofmulti-slot repetition PUCCHs overlap is exemplified, but the same methodmay be applied when there is overlapping between a multi-slot repetitionPUCCH and a PUCCH transmitted in a single slot.

Case 2-2) corresponds to a case where symbol unit overlap occurs betweenPUCCH for HARQ-ACK transmission and PUCCH for SR or CSI transmission, orPUCCH for multiple SR or CSI transmission. That is, Case 2-2)corresponds to a case where PUCCH #1 is repeatedly transmitted overmultiple slots (10-50, 10-51) and PUCCH #2 is also repeatedlytransmitted over multiple slots (10-60, 10-61), and a case where PUCCH#1 and PUCCH #2 overlap more than one symbol in one slot (10-70).

Between the PUCCHs where more than one symbol overlap occurs in thecorresponding slot (10-70), UCIs with higher priority may be transmittedby comparing the priority between UCIs in the PUCCH, and other UCIs maybe dropped from the corresponding slot. At this time, the prioritybetween the UCIs may follow an order of HARQ-ACK>SR>CSI.

In addition, when a plurality of CSI PUCCH resources overlap, a PUCCHcorresponding to a high priority CSI may be transmitted, and a PUCCHcorresponding to another CSI may be dropped from the corresponding slot.PUCCH transmission or dropping according to the above-described priorityis performed only in the slot in which symbol unit overlap occurs, andis not performed in other slots. That is, the PUCCH in which multi-slotrepetition is configured may be dropped in a slot in which symbol unitoverlap occurs, but may be transmitted in the remaining slots asconfigured.

In the above case, for the convenience of description, the case where aplurality of multi-slot repetition PUCCHs are overlapped is exemplified,but the same method may be applied when there is overlapping between amulti-slot repetition PUCCH and a PUCCH transmitted in a single slot.

Next, a method of generating a HARQ-ACK codebook for transmittingHARQ-ACK on the selected PUCCH resource will be described. When thedownlink data PDSCH is scheduled based on the DCI information of thePDCCH, the PDSCH is transmitted, and the slot information to which thecorresponding HARQ-ACK feedback is mapped and the mapping information ofthe uplink control channel PUCCH carrying HARQ-ACK feedback informationare transmitted. Specifically, the slot interval between the downlinkdata PDSCH and the corresponding HARQ-ACK feedback may be indicatedthrough the PDSCH-to-HARQ_feedback timing indicator, and one of eightfeedback timing offsets configured through a higher layer (e.g., RRCsignaling) may be indicated. In addition, in order to deliver PUCCHresources including the type of the uplink control channel PUCCH to mapHARQ-ACK feedback information, the location of the start symbol, and thenumber of mapping symbols, one of the 8 resources configured as an upperlayer through the PUCCH resource indicator may be indicated. Theterminal collects and transmits HARQ-ACK feedback bits to transmitHARQ-ACK information to the base station. In the following, thecollected HARQ-ACK feedback bits may be referred to as a mixture ofHARQ-ACK codebooks.

The base station may configure a Type-1 HARQ-ACK codebook to transmitHARQ-ACK feedback bits corresponding to a PDSCH that may be transmittedat a predetermined slot location regardless of whether or not an actualPDSCH is transmitted, for the terminal. Alternatively, the base stationmay configure a Type-2 HARQ-ACK codebook to manage and transmit HARQ-ACKfeedback bits corresponding to the actually transmitted PDSCH through acounter downlink assignment index (DAI) or total DAI, for the terminal.

When the terminal receives a Type-1 HARQ-ACK codebook, the terminal maydetermine a feedback bit to be transmitted through K 1 candidate values,which are HARQ-ACK feedback timing information for a PDSCH and a tableincluding slot, start symbol, number of symbols or length information towhich the PDSCH is mapped. The table including the start symbol, thenumber of symbols, or the length information of the PDSCH may beconfigured as higher layer signaling or may be determined as a defaulttable. Also, K1 candidate values may be determined as default values,for example, {1, 2, 3, 4, 5, 6, 7, 8} or higher layer signaling. Theslot to which the PDSCH is mapped can be known through the K1 value whenthe PDSCH is transmitted in a single slot, and if the PDSCH isrepeatedly transmitted in multiple slots (slot aggregation), an upperlayer parameter indicates the K1 value and the number of repetitivetransmissions, for example, a pdsch-AggregationFactor value configuredin the PDSCH-Config IE in the active BWP. If the PDSCH is repeatedlytransmitted in multiple slots, the K1 value is indicated based on thelast slot among the PDSCH repetitive transmissions, and the slot towhich the PDSCH is mapped is regarded as the pdsch-AggregationFactorslot from the last slot to be repeatedly transmitted, that is, the slotto start the repeated transmission.

Assuming that the set of PDSCH reception candidate cases in the servingcell c is M_(A,c), M_(A,c) may be determined in the following[pseudo-code 1] steps.

[Start Pseudo-Code 1]

-   -   Step 1: Initialize j to 0, M_(A,c) to be an empty set, and        HARQ-ACK transmission timing index k to 0.    -   Step 2: Configure R for a set of each row in a table including        slot, start symbol, number of symbols or length information to        which the PDSCH is mapped. If the symbol to which the PDSCH        indicated by each row of R is mapped is configured as an uplink        symbol according to the higher layer configuring, delete the        corresponding row from R.    -   Step 3-1: If the terminal receives one PDSCH for unicast in one        slot, and R is not an empty set, add k to the set M_(A,c).    -   Step 3-2: If the terminal receives more than one PDSCH in one        slot, count the maximum number of PDSCHs that may be assigned to        different symbols in R, increase the number of j by 1, and add        them to M_(A,c).    -   Step 4: Start again from step 2 and increase k by 1.        [End of Pseudo-Code 1]

HARQ-ACK feedback bits may be determined in the following [pseudo-code2] steps for M_(A and c) defined as [pseudo-code 1].

[Start Pseudo-Code 2]

-   -   Step 1: Initialize the HARQ-ACK reception occasion index m to 0        and the HARQ-ACK feedback bit index j to 0.    -   Step 2-1: If the terminal is indicated not to receive HARQ-ACK        bundling for a codeword through higher layer signaling, not to        receive CBG transmission of PDSCH, and to receive up to 2        codewords through 1 PDSCH, construct HARQ-ACK feedback bit for        each codeword by increasing j by 1.    -   Step 2-2: If the terminal is indicated to receive HARQ-ACK        bundling for a codeword through higher layer signaling, and is        indicated to receive up to 2 codewords through 1 PDSCH, compose        HARQ-ACK feedback bit for each codeword of one HARQ-ACK feedback        bit through binary AND operation.    -   Step 2-3: If the terminal is indicated to transmit CBG of the        PDSCH through higher layer signaling, and is not indicated to        receive up to 2 codewords through 1 PDSCH, construct HARQ-ACK        feedback bit for each codeword for the number of CBGs by        increasing j by 1.    -   Step 2-4: If the terminal is indicated to transmit the CBG of        the PDSCH through higher layer signaling, and is indicated to        receive up to 2 codewords through 1 PDSCH, construct HARQ-ACK        feedback bits for the number of CBGs by increasing j by 1 and        add to each codeword.    -   Step 2-5: If the terminal is not indicated to transmit CBG of        the PDSCH through higher layer signaling, and is not indicated        to receive up to 2 codewords through 1 PDSCH, construct a        HARQ-ACK feedback bit for each codeword.    -   Step 3: Start again from step 2-1 and increase m by 1.        [End of Pseudo-Code 2]

When the terminal receives the Type-2 HARQ-ACK codebook, the terminaldetermines a feedback bit to be transmitted through counter downlinkassignment index (DAI) or total DAI managing HARQ-ACK feedback bitscorresponding to PDSCH and K1 candidate values that are HARQ-ACKfeedback timing information for PDSCH. The K1 candidate values, whichare HARQ-ACK feedback timing information for the PDSCH, are composed ofa combination of default values and values specified through higherlayer signaling. For example, the default values may be configured as{1, 2, 3, 4, 5, 6, 7, 8}.

If the counter DAI of DCI format 1_0 or DCI format 1_1 in which thePDSCH is allocated in the serving cell c is called V_(C-DAI,c,m) ^(DL)for the PDCCH monitoring timing m, and the total DAI of DCI format 1_1in which the PDSCH is allocated to the uplink control channel PDCCHmonitoring timing m is V_(T-DAI,c,m) ^(DL), a Type-2 HARQ-ACK codebookmay be configured in the following [pseudo-code 3] steps.

[Start Pseudo-Code 3]

-   -   Step 1: Initialize serving cell index c to 0, PDCCH monitoring        timing m to 0, j to 0, DAI comparison index V_(temp), V_(temp)        to 0, and HARQ-ACK feedback bit set VS to be an empty set.    -   Step 2: If the PDCCH monitoring timing m is before the downlink        BWP change for the serving cell c or before the uplink BWP        change for the PCell, and the downlink BWP change is not        triggered due to DCI format 1_1 of the PDCCH monitoring timing        m, c is excluded from the serving cell set.    -   Step 3-1: If the PDSCH allocated by the PDCCH corresponding to        the PDCCH monitoring timing m exists in the serving cell c, and        if V_(C-DAI,c,m) ^(DL) is less than or equal to V_(temp), j is        increased by 1 and V_(temp) is configured as V_(C-DAI,c,m)        ^(DL). In addition, if V_(T-DAI,c,m) ^(DL) is an empty set,        V_(temp2) is configured as V_(C-DAI,c,m) ^(DL), and if        V_(T-DAI,c,m) ^(DL) is not an empty set, V_(temp2) is configured        as V_(T-DAI,c,m) ^(DL).    -   Step 3-2: If the PDSCH allocated by the PDCCH corresponding to        the PDCCH monitoring timing m exists in the serving cell c, and        the terminal is indicated not to receive HARQ-ACK bundling for        the codeword through higher layer signaling and indicated to        receive up to two codewords from at least one downlink BWP of at        least one serving cell through one PDSCH, construct HARQ-ACK        feedback bit for each codeword by increasing j by 1.    -   Step 3-3: If the PDSCH allocated by the PDCCH corresponding to        the PDCCH monitoring timing m exists in the serving cell c, and        the terminal is indicated to receive HARQ-ACK bundling for the        codeword through higher layer signaling and indicated to receive        up to two codewords from at least one downlink BWP of at least        one serving cell through one PDSCH, compose HARQ-ACK feedback        bit for each codeword of one HARQ-ACK feedback bit through a        binary AND operation.    -   Step 3-4: If the PDSCH allocated by the PDCCH corresponding to        the PDCCH monitoring timing m exists in the serving cell c, and        the terminal is not indicated to receive up to two codewords        through one PDSCH, construct HARQ-ACK feedback bit for one        codeword.    -   Step 4: Start again from Step 2 and increase c by 1.    -   Step 5: Start again from Step 2 and increase m by 1.    -   Step 6: Increase j by 1 when V_(temp2) is less than V_(temp).    -   Step 7-1: If the terminal is indicated not to bundle HARQ-ACK        for the codeword through higher layer signaling, and instructed        to receive up to 2 codewords from at least one downlink BWP of        at least one serving cell through one PDSCH, configure the total        number of HARQ-ACK feedback bits as 2·(4·j+V_(temp2)).    -   Step 7-2: If the terminal is indicated to bundle HARQ-ACK for        the codeword through higher layer signaling, or is not        instructed to receive up to 2 codewords through 1 PDSCH,        configure the total number of HARQ-ACK feedback bits as        4·j+V_(temp2).    -   Step 8: Determine HARQ-ACK feedback bits with NACK for HARQ-ACK        feedback bits not configured in steps 3-1, 3-2, 3-3 and 3-4.        [End of Pseudo-Code 3]

FIG. 11 illustrates a view for a base station and a terminal radioprotocol structure when performing single cell, carrier aggregation, anddual connectivity according to an embodiment. Referring to FIG. 11, theradio protocols of a next-generation mobile communication system includean NR service data adaptation protocol (SDAP) 1125 and 1170, an NRpacket data convergence protocol (PDCP) 1130 and 1165, and an NR radiolink control (RLC) 1140 and 1155 in the terminal and the NR base station1135 and 1160, and NR medium access control (MAC), respectively.

The main functions of the NR SDAPs 1125 and 1170 may include some of thefollowing functions.

-   -   Transfer of user plane data    -   Mapping between a QoS flow and a DRB for both DL and UL    -   Marking QoS flow ID in both DL and UL packets    -   Mapping reflective QoS flow to DRB for the UL SDAP PDUs

For the SDAP layer device, the terminal may be configured as to whetherto use the header of the SDAP layer device for each PDCP layer device,for each bearer, or for each logical channel, or whether to use thefunction of the SDAP layer device through an RRC message, and when theSDAP header is configured, the NAS QoS reflection configuration 1-bitindicator (NAS reflective QoS) of the SDAP header and the AS QoSreflection configuration 1-bit indicator (AS reflective QoS) indicatethat the terminal may update or reconfigure the QoS flow of uplink anddownlink and mapping information for the data bearer. The SDAP headermay include QoS flow ID information indicating QoS. The QoS informationmay be used as data processing priority and scheduling information tosupport a smooth service.

The main functions of NR PDCP 10-30 and 10-65 may include some of thefollowing functions.

-   -   Header compression and decompression: ROHC only    -   Transfer of user data    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   PDCP PDU reordering for reception    -   Duplicate detection of lower layer SDUs    -   Retransmission of PDCP SDUs    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

In the above, the order reordering function of the NR PDCP device refersto a function of reordering PDCP PDUs received from a lower layer inorder based on a PDCP sequence number (SN), may include a function ofdelivering data to an upper layer in the reordered order, may include afunction of directly transmitting without considering the order, mayinclude a function of reordering and recording lost PDCP PDUs, mayinclude a function of transmitting a status report for the lost PDCPPDUs to the transmitting side, or may include a function of requestingretransmission of lost PDCP PDUs.

The main functions of the NR RLCs 1135 and 1160 may include some of thefollowing functions.

-   -   Transfer of upper layer PDUs    -   In-sequence delivery of upper layer PDUs    -   Out-of-sequence delivery of upper layer PDUs    -   Error Correction through ARQ    -   Concatenation, segmentation and reassembly of RLC SDUs    -   Re-segmentation of RLC data PDUs    -   Reordering of RLC data PDUs    -   Duplicate detection    -   Protocol error detection    -   RLC SDU discard    -   RLC re-establishment

In the above, the in-sequence delivery of the NR RLC device refers to afunction of sequentially transmitting RLC SDUs received from a lowerlayer to an upper layer, and may include a function of reassembling anddelivering when one RLC SDU is originally divided into multiple RLC SDUsand received, may include a function of rearranging the received RLCPDUs, based on RLC sequence number (SN) or PDCP sequence number (SN),may include a function of reordering and recording lost RLC PDUs, mayinclude a function of reporting the states of the lost RLC PDUs to atransmitting side, may include a function of requesting retransmissionof lost RLC PDUs, may include a function of forwarding only RLC SDUsbefore the lost RLC SDU in order when there is a lost RLC SDU, mayinclude a function of delivering all RLC SDUs received before the timerstarts in order to a higher layer if a predetermined timer expires evenif there is a lost RLC SDU, or may include a function of delivering allRLC SDUs received to the upper layer in order if a predetermined timerexpires even if there is a lost RLC SDU. In addition, the RLC PDUs maybe processed in the order in which they are received (regardless of theserial number or sequence number, in order of arrival) and delivered tothe PDCP device in any order (out-of-sequence delivery), and in the caseof a segment, segments that are stored in a buffer or to be received ata later time may be received and reconstructed into a complete RLC PDU,processed, and then transmitted to a PDCP device. The NR RLC layer mightnot include a concatenation function, and the function may be performedin the NR MAC layer or replaced by a multiplexing function of the NR MAClayer.

In the above, out-of-sequence delivery of the NR RLC device refers to afunction of directly transmitting RLC SDUs received from a lower layerto an upper layer regardless of order, and may include a function ofreassembling and delivering when one RLC SDU is originally divided intomultiple RLC SDUs and received, or may include a function of storing theRLC SN or PDCP SN of the received RLC PDUs and sorting the order torecord the lost RLC PDUs.

The NR MACs 1140 and 1155 may be connected to several NR RLC layerdevices configured in one terminal, and the main functions of the NR MACmay include some of the following functions.

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

The NR PHY layer 1145 and 1150 may perform channel coding and modulatingthe upper layer data, making an OFDM symbol and transmitting the same toa radio channel, or demodulating and channel decoding an OFDM symbolreceived through the radio channel to deliver the same to the upperlayer.

The detailed structure of the radio protocol structure may be changedaccording to a carrier (or cell) operation method. For example, when abase station transmits data to a terminal based on a single carrier (orcell), the base station and the terminal use a protocol structure havinga single structure for each layer, such as 1100. On the other hand, whena base station transmits data to a terminal, based on carrieraggregation (CA) using multiple carriers in a single TRP, the basestation and the terminal have a single structure up to RLC like 1110,but use a protocol structure for multiplexing the PHY layer through theMAC layer. As another example, when a base station transmits data to aterminal, based on dual connectivity (DDC) using multiple carriers inmultiple TRPs, the base station and the terminal have a single structureup to RLC as in 1120, but use a protocol structure for multiplexing thePHY layer through the MAC layer.

Referring to the PUCCH-related descriptions above, the current Rel-15 NRis focused on PDSCH transmission from a single cell/transmissionpoint/panel/beam (hereinafter referred to as a transmission receptionpoint (TRP)), or coherent PDSCH transmission for multiple TRPs, and onlyone PUCCH resource for HARQ-ACK is transmitted within one slot as aHARQ-ACK transmission method.

On the other hand, NR release 16 supports non-coherent transmission foreach TRP, that is, non-coherent joint transmission (NC-JT). At thistime, each TRP participating in NC-JT may transmit a separate PDSCH tothe terminal at the same time. HARQ-ACK information for the PDSCHs maybe transmitted through one PUCCH resource, and the HARQ-ACK informationmay be transmitted through a separate PUCCH resource for each TRP inconsideration of a case in which overhead due to information exchangebetween TRPs is burdensome, such as a case where a backhaul delay timefor each TRP is long. Particularly, when HARQ-ACK information (or UCIinformation) is transmitted through a separate PUCCH resource forHARQ-ACK transmission for each TRP, the HARQ-ACK information may betransmitted through TDM in a slot. The treatment method for overlapbetween PUCCH resources was not defined in Rel-15. In the disclosure, byproviding a processing method for the above-described case, the loss ofuplink control information and transmission delay time in NC-JTtransmission can be minimized. Meanwhile, the disclosure can be appliedregardless of whether NC-JT transmission is performed when a pluralityof PUCCH resources for HARQ-ACK transmission are included in one slot.

Hereinafter, embodiments of the disclosure will be described in detailin conjunction with the accompanying drawings. In the followingdescription of the disclosure, a detailed description of known functionsor configurations incorporated herein will be omitted when it may makethe subject matter of the disclosure rather unclear. The terms whichwill be described below are terms defined in consideration of thefunctions in the disclosure, and may be different according to users,intentions of the users, or customs. Therefore, the definitions of theterms should be made based on the contents throughout the specification.

Hereinafter, a base station is a subject that performs resourceallocation of a terminal, and may be at least one of a gNode B (gNB), aneNode B (eNB), a Node B, a base station (BS), a radio access unit, abase station controller, or a node on a network. The terminal mayinclude a user equipment (UE), a mobile station (MS), a cellular phone,a smart phone, a computer, or a multimedia system capable of performingcommunication functions. In addition, NR or LTE/LTE-A systems will bedescribed below as an example, but embodiments of the disclosure may beapplied to other communication systems having similar technicalbackgrounds or channel types. In addition, the embodiments of thedisclosure may be applied to other communication systems through somemodifications within a range not departing greatly from the scope of thedisclosure as determined by a person having skilled technical knowledge.

The content of the disclosure is applicable to FDD and TDD systems.

Hereinafter, in the disclosure, high-level signaling is a signaltransmission method transmitted from a base station to a terminal usinga downlink data channel of a physical layer, or a signal transmissionmethod transmitted from a terminal to a base station using an uplinkdata channel of a physical layer, and may be referred to as RRCsignaling, PDCP signaling, or medium access control (MAC) controlelement (MAC CE).

Hereinafter, in the disclosure, in determining whether to applycooperative communication, the terminal may use various methods in whichthe PDCCH(s) allocating the PDSCH to which the cooperative communicationis applied has a specific format, the PDCCH(s) allocating the PDSCH towhich the cooperative communication is applied includes a specificindicator indicating whether the cooperative communication is applied,PDCCH(s) allocating PDSCH to which cooperative communication is appliedis scrambled with a specific RNTI, or the application of cooperativecommunication in a specific section indicated by the upper layer isassumed. Hereinafter, for the convenience of description, receiving thePDSCH to which the cooperative communication is applied based onconditions similar to the above by the terminal will be referred to asan NC-JT case

Hereinafter, in the disclosure, determining the priority between A and Bmay be variously applied such as selecting one having a higher priorityaccording to a predetermined priority rule to perform an operationcorresponding thereto, or omitting or dropping an operation for a lowerpriority.

Hereinafter, in the disclosure, the above examples will be describedthrough a number of embodiments, but these are not mutually independent,and it is possible that one or more embodiments may be appliedsimultaneously or in combination.

First Embodiment: DCI Reception for NC-JT

The 5G wireless communication system, unlike before, may support notonly services requiring a high transmission speed, but also serviceshaving a very short transmission delay and services requiring a highconnection density. In a wireless communication network including aplurality of cells, transmission and reception points (TRP), or beams,the coordinated transmission between each cell, TRP, and/or beam is oneof the basic technologies that can satisfy various service requirementsby increasing the strength of signals received by the terminal orefficiently performing interference control between cells, TRPs or/andbeams.

Joint transmission (JT) is a representative transmission technique forcooperative communication as described above, and supports one terminalthrough different cells, TRP, and/or beams through the jointtransmission technique to increase the strength of the signal receivedby the terminal. Meanwhile, since channels of each cell, TRP or/and beamand a terminal may have significantly different characteristics,different precodings, modulation and coding schemes (MCS), and resourceassignments need to be applied to links between each cell, TRP or/andbeam and the terminal. In particular, in the case of non-coherent jointtransmission (NC-JT) supporting non-coherent precoding between eachcell, TRP or/and beam, it is important to configure individual DL(downlink) transmission information for each cell, TRP or/and beam.Meanwhile, individual DL transmission information configuration for eachcell, TRP, and/or beam is a major factor in increasing the payloadrequired for DL DCI transmission, which may adversely affect thereception performance of a physical downlink control channel (PDCCH)transmitting DCI. Therefore, it is necessary to carefully design atradeoff between DCI information amount and PDCCH reception performancefor JT support.

FIG. 12 illustrates a view for an example of antenna port configurationand resource allocation for cooperative communication according to someembodiments in a wireless communication system according to anembodiment.

Referring to FIG. 12, examples of joint resource allocation according toTRP according to a joint transmission (JT) technique and situation areillustrated. In FIG. 12, 1200 is an example of coherent jointtransmission (C-JT) supporting coherent precoding between each cell, TRPor/and beam. In C-JT, a single data (PDSCH) is transmitted from the TRPA (1205) and the TRP B (1210) to the terminal 1215, and joint precodingmay be performed in multiple TRPs. This may mean that TRP A (1205) andTRP B (1210) transmit DMRS through the same DMRS ports (e.g., DMRS portsA and B in both TRPs) for receiving the same PDSCH. In this case, theterminal may receive one DCI information for receiving one PDSCHdemodulated based on DMRS transmitted through DMRS ports A and B.

In FIG. 12, 1220 is an example of non-coherent joint transmission(NC-JT) supporting non-coherent precoding between each cell, TRP or/andbeam.

In the case of NC-JT, PDSCH may be transmitted to the terminal 1235 foreach cell, TRP or/and beam, and precoding may be individually applied toeach PDSCH. Each cell, TRP or/and beam transmits different PDSCHs toimprove throughput compared to a single cell, TRP or/and beamtransmission, or each cell, TRP or/and beam may repeatedly transmit thesame PDSCH, thereby improving reliability compared to a single cell, TRPor/and beam transmission. Various radio resource allocations may beconsidered, such as when the frequency and time resources used bymultiple TRPs for transmitting PDSCH are all the same (1240), when thefrequency and time resources used by multiple TRPs do not overlap at all(1245), or when some of the frequency and time resources used bymultiple TRPs overlap (1250). When multiple TRPs repeatedly transmit thesame PDSCH to improve reliability in each case for the above-mentionedradio resource allocation, if the receiving terminal does not knowwhether the corresponding PDSCH is repeatedly transmitted, thecorresponding terminal may have limitations in improving reliabilitybecause the terminal cannot perform combining in the physical layer forthe corresponding PDSCH. Therefore, the disclosure provides a repeattransmission instruction and configuration method for improving NC-JTtransmission reliability.

For NC-JT support, DCIs of various forms, structures, and relationshipsmay be considered to simultaneously allocate multiple PDSCHs to oneterminal.

FIG. 13 illustrates a view for an example of downlink controlinformation (DCI) configuration for cooperative communication in awireless communication system according to an embodiment.

Referring to FIG. 13, four examples of DCI design for NC-JT support areillustrated. Referring to FIG. 13, case #1 (1300) is an example in whichthe control information for PDSCH transmitted in (N−1) additional TRPsis transmitted in the same form (same DCI format) as the controlinformation for a PDSCH transmitted in a serving TRP, in a situation inwhich different (N−1) PDSCHs are transmitted from (N−1) additional TRPs(TRP #1 to TRP #(N−1)) in addition to the serving TRP (TRP #0) used whentransmitting a single PDSCH. That is, the terminals may obtain controlinformation for PDSCHs transmitted from different TRPs (DCI #0 to DCI#(N−1)) through DCIs having the same DCI format and the same payload(TRP #0 to TRP #(N−1)).

In case #1 described above, the degree of freedom for each PDSCH control(assignment) may be completely guaranteed, but when each DCI istransmitted in different TRPs, a coverage difference for each DCI mayoccur and reception performance may be deteriorated.

Case #2 (1305) is an example in which the control information for aPDSCH transmitted from (N−1) additional TRPs is transmitted in adifferent form (different DCI format or different DCI payload) from thecontrol information for a PDSCH transmitted from the serving TRP, in asituation in which different (N−1) PDSCHs are transmitted in (N−1)additional TRPs (TRP #1 to TRP #(N−1)) in addition to the serving TRP(TRP #0) used when transmitting a single PDSCH. For example, in the caseof DCI #0 that transmits control information for a PDSCH transmitted inthe serving TRP (TRP #0), all information elements of DCI format 1_0 toDCI format 1_1 are included, but in the case of ‘shortened’ DCIs (sDC #0to sDCI #(N−2)) transmitting control information for PDSCHs transmittedfrom the cooperative TRP (TRP #1 to TRP #(N−1)), some of the informationelements of DCI format 1_0 to DCI format 1_1 may be included. Therefore,in the case of sDCI that transmits control information for PDSCHstransmitted in the cooperative TRP, the payload may possibly be smallcompared to the normal DCI (nDCI) transmitting PDSCH-related controlinformation transmitted from the serving TRP, or the payload maypossibly include as many reserved bits as the number of bits less thanthe nDCI.

In case #2 described above, the degree of freedom of each PDSCH control(assignment) may be limited according to the contents of the informationelements included in the sDCI, but since the reception performance ofsDCI is superior to that of nDCI, the probability of occurrence of acoverage difference for each DCI may be lowered.

Case #3 (1310) is an example in which the control information for PDSCHstransmitted from (N−1) additional TRPs is transmitted in a differentformat (different DCI format or different DCI payload) from controlinformation for PDSCHs transmitted from the serving TRP, in a situationin which (N−1) PDSCHs are transmitted from (N−1) additional TRPs (TRP #1to TRP #(N−1)) other than the serving TRP (TRP #0) used whentransmitting a single PDSCH. For example, in the case of DCI #0transmitting control information for PDSCH transmitted in serving TRP(TRP #0), all information elements of DCI format 1_0 to DCI format 1_1are included, and in the case of control information for PDSCHstransmitted from a cooperative TRP (TRP #1 to TRP #(N−1)), only some ofthe information elements of DCI format 1_0 to DCI format 1_1 may becollected and transmitted in one ‘secondary’ DCI (sDCI). For example,the sDCI may have at least one of HARQ-related information, such asfrequency domain resource assignment, time domain resource assignment,and MCS of cooperative TRPs. In addition, for information not includedin sDCI, such as a bandwidth part (BWP) indicator or a carrierindicator, the information may follow the DCI (DCI #0, normal DCI, nDCI)of serving TRP.

In case #3, the degree of freedom of each PDSCH control (assignment) maybe limited according to contents of information elements included insDCI, but the reception performance of sDCI can be adjusted and comparedto case #1 or case #2, and the complexity of DCI blind decoding can bereduced.

Case #4 (1315) is an example of transmitting control information forPDSCHs transmitted from (N−1) additional TRPs in DCI (long DCI, IDCI) ascontrol information for PDSCHs transmitted from the serving TRP, in asituation in which (N−1) PDSCHs are transmitted from (N−1) additionalTRPs (TRP #1 to TRP #(N−1)) other than the serving TRP (TRP #0) usedwhen transmitting a single PDSCH. That is, the terminal may acquirecontrol information for PDSCHs transmitted from different TRPs (TRP #0to TRP #(N−1)) through a single DCI. In case #4, the complexity of DCIblind decoding of the terminal may not increase, but the PDSCH control(assignment) degree of freedom may be low, such as having a limitednumber of cooperative TRPs due to long DCI payload limitation.

In the following description and embodiments, sDCI may refer to variousauxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (PDIformat 1_0 to 1_1 described above) including PDSCH control informationtransmitted from a cooperative TRP. If no special restrictions arespecified, the description is similarly applicable to the variousauxiliary DCIs.

In the following descriptions and embodiments, the above-described case#1, case #2, and case #3 in which one or more DCIs (PDCCH) are used forNC-JT support are divided into multiple PDCCH-based NC-JTs, and a singleDCI (for NC-JT support) (PDCCH) may be classified as a single PDCCHbased NC-JT in case a of the above-described case #4.

In embodiments of the disclosure, “cooperative TRP” may be replaced withvarious terms such as “cooperative panel” or “cooperative beam” whenactually applied.

In embodiments of the disclosure, the term “when NC-JT is applied” maybe interpreted in various ways according to the situation, such as “whena terminal receives one or more PDSCHs simultaneously from one BWP”,“when a terminal receives two or more PDSCHs simultaneously from oneBWP, based on transmission configuration indicator (TCI) indication”,“when the terminal receives PDSCH associated with one or more DMRS portgroup (port group)”, etc., but it is used as one expression forconvenience of explanation.

In the disclosure, the radio protocol structure for NC-JT may be used invarious ways depending on the TRP deployment scenario. For example, ifthere is no or little backhaul delay between cooperative TRPs, it ispossible to use a structure, based on MAC layer multiplexing similar to1110 of FIG. 11 (CA-like method). On the other hand, when the backhauldelay between cooperative TRPs is so large that the backhaul delaycannot be ignored (e.g., when 2 milliseconds (ms) or more is requiredfor information exchange such as CSI, scheduling, and HARQ-ACK betweencooperative TRPs), a robust characteristic in delay may possibly besecured using an independent structure for each TRP from the RLC layer(DC-like method), similar to 1120 of FIG. 11.

Embodiment 1-1: Method of Configuring Downlink Control Channel for NC-JTTransmission on the Basis of Multi-PDCCH

In multiple PDCCH-based NC-JT, when transmitting DCI for a PDSCHschedule of each TRP, there may be a CORESET or search space classifiedfor each TRP. CORSET or search space for each TRP may be configured asat least one of the following cases.

-   -   Upper layer index configuration by CORESET: The TRP that        transmits the PDCCH in the corresponding CORESET may be        distinguished by the upper layer index value for each set        CORESET. That is, in the set of CORESETs having the same upper        layer index value, it may be considered that the same TRP        transmits the PDCCH or the PDCCH that schedules the PDSCH of the        same TRP is transmitted.    -   Multiple PDCCH-Config configuration: Multiple PDCCH-Configs in        one BWP are configured, and each PDCCH-Config may be considered        to be configured for each TRP PDCCH. Here, a list of        TRP-specific CORESET and/or a list of search spaces by TRP may        be configured.    -   CORESET beam/beam group configuration: The TRP corresponding to        the corresponding CORESET may be identified through the beam or        beam group set for each CORESET. For example, when the same TCI        state is configured in a plurality of CORESETs, the        corresponding CORESETs may be considered to be transmitted        through the same TRP or a PDCCH that schedules the PDSCH of the        same TRP in the corresponding CORESET may be transmitted.    -   Search space beam/beam group configuration: A beam or beam group        is configured for each search space, and through this, TRP for        each search space may be classified. For example, when the same        beam/beam group or TCI state is configured in a plurality of        search spaces, in the search space, it may be considered that        the same TRP transmits the PDCCH, or it may be considered that        the PDCCH that schedules the PDSCH of the same TRP is        transmitted in the search space.

By dividing the CORESET or search space for each TRP as described above,PDSCH and HARQ-ACK information may be classified for each TRP, and thus,an independent HARQ-ACK codebook for each TRP may be generated andindependent PUCCH resources may be used.

Second Embodiment: HARQ-ACK Information Transmission Method for NC-JTTransmission

The following embodiment provides a detailed method of transmittingHARQ-ACK information for NC-JT transmission.

FIG. 14A illustrates a view for HARQ-ACK reporting for non-coherentjoint transmission (NC-JT) transmission according to an embodiment, FIG.14B is a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment, FIG. 14Cis a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment, and FIG.14D is a view illustrating HARQ-ACK reporting for non-coherent jointtransmission (NC-JT) transmission according to an embodiment.

First, FIG. 14A (option #1: HARQ-ACK for single-PDCCH NC-JT) 14-00illustrates a situation in which HARQ-ACK information for one or aplurality of PDSCHs 14-05 scheduled by TRP is transmitted through onePUCCH resource 14-10 in the case of single-PDCCH-based NC-JT. The PUCCHresource may be indicated through the PRI value and K₁ value in DCIdescribed above.

FIG. 14B (option #2) to FIG. 14D (option #4) 14-20, 14-40, 14-60illustrate a case of a multi-PDCCH based NC-JT. At this time, eachoption may be classified according to the number of PUCCH resources totransmit HARQ-ACK information corresponding to the PDSCH of each TRP andthe position on the time axis of the PUCCH resource.

FIG. 14B (option #2: joint HARQ-ACK) 14-20 illustrates a situation inwhich HARQ-ACK information corresponding to PDSCHs 14-25 and 14-26 ofeach TRP is transmitted through one PUCCH resource. All HARQ-ACKinformation for each TRP may be generated based on a single HARQ-ACKcodebook, or HARQ-ACK information for each TRP may be generated based onan individual HARQ-ACK codebook.

When individual HARQ-ACK codebooks for each TRP are used, the TRP may beclassified based on at least one of a set of CORESETs having the sameupper layer index, a set of CORESETs belonging to the same TCI state,beam or beam group, or a set of search spaces belonging to the same TCIstate, beam or beam group as defined in Example 1-1.

FIG. 14C (option #3: inter-slot time division multiplexed (TDMed)separate HARQ-ACK) 14-40 illustrates a situation in which HARQ-ACKinformation corresponding to PDSCHs 14-45 and 14-46 of each TRP istransmitted through PUCCH resources 14-50 and 14-51 of different slots14-52 and 14-53. The slot through which the PUCCH resource for each TRPis transmitted may be determined by the above-described K₁ value. If theK₁ values indicated by multiple PDCCHs indicate the same slot, all ofthe corresponding PDCCHs may be considered to be scheduled in the sameTRP and all HARQ-ACK information corresponding thereto may betransmitted.

FIG. 14D (option #4: intra-slot TDMed separate HARQ-ACK) 14-60illustrates a situation in which HARQ-ACK information corresponding toPDSCHs 14-65 and 14-66 of each TRP is transmitted in different symbolsin the same slot 14-75 through different PUCH resources 14-70 and 14-71.The slot through which the PUCCH resource for each TRP is transmittedmay be determined by the above-described K₁ value, and if the K₁ valuesindicated by multiple PDCCHs indicate the same slot, at least one of thefollowing methods determines PUCCH resource selection and transmissionsymbols

-   -   Configure PUCCH resource group for each TRP

A PUCCH resource group for HARQ-ACK transmission for each TRP may beconfigured. When the TRP for each CORESET/search space is classified asin Example 1-1, the PUCCH resource for HARQ-ACK transmission by TRP maybe selected in the PUCCH resource group for the corresponding TRP. TDMmay be expected between PUCCH resources selected from different PUCCHresource groups, that is, it may be expected that the selected PUCCHresources do not overlap in units of symbols. As described above, anindividual HARQ-ACK codebook for each TRP may be generated andtransmitted to the PUCCH resource selected for each TRP.

-   -   Indicate different PRI for each TRP

When TRP for each CORESET/search space is classified as in Example 1-1,a PUCCH resource for each TRP may be selected according to PRI. That is,the PUCCH resource selection process in Rel-15 described above may beindependently performed for each TRP. At this time, the PRI used todetermine PUCCH resource for each TRP may be different. For example, theterminal might not expect that PRI used for PUCCH resource determinationfor each TRP is indicated with the same value. In addition, TDM may beexpected between PUCCH resources corresponding to PRI for each TRP. Thatis, it may be expected that the selected PUCCH resources do not overlapin a symbol unit. As described above, an individual HARQ-ACK codebookfor each TRP may be generated and transmitted to the PUCCH resourceselected for each TRP.

-   -   Define K₁ value in sub-slot units

The PUCCH resource selection process in Rel-15 is as follows, but avalue may be defined in units of sub-slots. For example, a HARQ-ACKcodebook for PDSCH/PDCCHs indicated to report HARQ-ACK in the samesub-slot may be generated and transmitted through a PUCCH resourceindicated as PRI. The HARQ-ACK codebook generation and PUCCH resourceselection process may be irrespective of whether TRP is classified foreach CORESET/search space.

When the terminal supports NC-JT reception, one of the options may beconfigured through the upper layer or may be implicitly selecteddepending on the situation. For example, one of option 2 and option 3/4may be configured for a terminal supporting multi-PDCCH-based NC-JT asan upper layer. As another example, depending on whethersingle-PDCCH-based NC-JT or multi-PDCCH-based NC-JT issupported/configured, option 1 may be selected for thesingle-PDCCH-based NC-JT and one of options 2/3/4 may be selected forthe multi-PDCCH-based NC-JT. As another example, in multi-PDCCH-basedNC-JT, an option used may be determined according to selection of PUCCHresource. When PUCCH resources of the same slot are selected fromdifferent TRPs, if the corresponding PUCCH resources are different anddo not overlap in symbol units, the HARQ-ACK may be transmittedaccording to option 4, and if the PUCCH resources overlap in symbolunits or are identical, the HARQ-ACK may be transmitted according tooption 2. When PUCCH resources of different slots are selected fromdifferent TRPs, the HARQ-ACK may be transmitted according to option 3.The configuration for the options may be dependent on terminalcapability. For example, the base station may receive the terminalcapability according to the above-described procedure, and may configurethe option, based on this. For example, option 4 configuration may beallowed for a terminal supporting intra-slot TDMed separate HARQ-ACK,and a terminal that does not have the capability may not expect theconfiguration according to option 4.

Third Embodiment: PUCCH-PUCCH Overlap Processing Method forMulti-PDCCH-Based NC-JT

In the multi-PDCCH-based NC-JT, when the intra-slot TDMed separateHARQ-ACK is used, multiple HARQ-ACKs within one slot may be transmittedthrough PUCCH resources. This is different from Rel-15, which is limitedso that only one HARQ-ACK is transmitted in one slot. Therefore, in thisembodiment, a specific processing method for a case where overlapbetween the PUCCH resource for HARQ-ACK and the PUCCH resource for otheruplink control information occurs is presented.

In this embodiment, a method for a case where overlap between PUCCHresources in which multi-repetition is not configured occurs will bedescribed first. At this time, the following two cases shown in FIG. 15will be described.

FIG. 15A illustrates a view for a case where overlap occurs betweenPUCCH resources according to an embodiment.

Referring to FIG. 15A, case 1 (15-10) shows a case where overlap occursbetween PUCCH resources #1 and #2 (15-11 and 15-12) for HARQ-ACKtransmission and other PUCCH resources #3 (15-13).

Case 2 (15-20) shows a case where overlap occurs between PUCCH resource#1 (15-21) for HARQ-ACK transmission and other PUCCH resource #3(15-23).

Depending on the TRP-specific PUCCH resource configuration and theHARQ-ACK transmission method described in Example 2, some of the abovecases might not occur.

For example, in a situation where joint HARQ-ACK to inter-slot TDMedseparate HARQ-ACK is applied, only Case 2 may occur.

On the other hand, in the situation where intra-slot TDMed separateHARQ-ACK is applied, both Case 1 and Case 2 may occur.

As another example, some of the above cases might not occur depending onwhether a PUCCH resource group for each TRP described in Example 2 isconfigured. If all PUCCH resources are classified according to theTRP-specific PUCCH resource group, only Case 2 may occur. On the otherhand, in a situation where the PUCCH resource group for each TRP is notconfigured or only PUCCH resources for HARQ-ACK transmission areclassified according to the PUCCH resource group for each TRP, both Case1 and Case 2 may occur.

A method of processing PUCCH according to the overlap of PUCCH resourcesaccording to FIG. 15A will be described in FIG. 15B.

FIG. 15B illustrates a view for a method of transmitting PUCCH whenoverlap occurs between PUCCH resources according to an embodiment.

Referring to FIG. 15B, the terminal may receive configurationinformation related to PUCCH resources in operation 1530. Theconfiguration information may be received through higher layersignaling.

At this time, the configuration information may include one or morePUCCH resource sets as described above, and one or more PUCCH resourcesmay be included in one PUCCH resource set. For details, refer to theabove.

In addition, the terminal may receive DCI including resource allocationinformation in operation 1540. The resource allocation information mayinclude at least one of information on resources for receiving downlinkdata and information on resources for transmitting uplink controlinformation.

At this time, the information on the resource for transmitting theuplink control information may include an indicator indicating the PUCCHresource received through the configuration information. In addition, itmay include information K1 about the slot location for transmitting thePUCCH resource. For details, refer to the above.

In addition, when the terminal supports NC-JT reception, the terminalmay receive DCI for each TRP. At this time, as a method of receiving theDCI, various methods proposed in FIG. 13 may be used. For details, referto the above.

In addition, the terminal may identify the PUCCH resource to transmitthe uplink control information in step 1550. The terminal may identifythe PUCCH resource, based on at least one of the configurationinformation or DCI.

When the NC-JT is configured in the terminal, the terminal may transmitUCI for a plurality of TRPs and may identify a plurality of PUCCHresources. At this time, when the identified plurality of PUCCHresources are located in one slot, PUCCH resource groups may beconfigured for each TRP as described above, different PRIs may beindicated for each TRP, or K1 values included in DCI may be defined inunits of sub-slots to be allocated to other symbols within one slot. Fordetails, refer to the above.

On the other hand, the terminal may transmit the capability informationon whether or not to transmit the multiplexed control information forHARQ-ACK transmission through the TDM PUCCH resource in one slot to thebase station, and the base station may configure a plurality of PUCCHresources for HARQ-ACK transmission in one slot as described above onlywhen the terminal has the capability. The details related to thecapability transmission/reception method and transmission/reception timepoint are the same as described above, and will be omitted below.

When two or more PUCCH resources (PUCCH #1, PUCCH #2) are located in oneslot, at the same time, PUCCH resources (PUCCH #3) for different UCItransmissions may be allocated to the same slot. At this time, otheruplink information may include SR, CSI, etc., or may include HARQ-ACKinformation for other TRP. Meanwhile, for the convenience ofdescription, PUCCH #1 and PUCCH #2 that are TDM on a time axis amongPUCCH resources illustrated in FIG. 15A may be referred to as a firstPUCCH and PUCCH #3 as a second PUCCH. Alternatively, PUCCH #1, PUCCH #2,and PUCCH #3 may be referred to as a first PUCCH, a second PUCCH, and athird PUCCH, respectively.

Therefore, the terminal may identify whether an overlap has occurredbetween PUCCH resources in operation 1560. At this time, the terminalmay identify whether an overlap has occurred between the PUCCH resource(e.g., TDM PUCCH resource in the slot) identified in operation 1550 andanother PUCCH resource. At this time, another PUCCH resource may mean aresource for transmitting different UCIs (e.g., UCIs except HARQ-ACK).As described above, the PUCCH resources (PUCCH #1, PUCCH #2) identifiedin operation 1550 may be referred to as a first PUCCH and another PUCCHresource (PUCCH #3) as a second PUCCH.

At this time, overlap between PUCCH resources may mean an overlap in aunit of symbols. Therefore, operation 1560 may refer to an operation ofidentifying whether there is a PUCCH resource overlapping with the TDMPUCCH resource in the slot as shown in FIG. 15A.

As a result of identification, if an overlap does not occur, theterminal may transmit UCI through each PUCCH resource. For example, ifthe PUCCH resource corresponding to each of the TRP 1 and TRP2 isincluded in one slot and intra-slot TDMed separate HARQ-ACK isconfigured, the terminal may multiplex and transmit HARQ-ACK informationfor each TRP to PUCCH resources for each TRP. At this time, the PUCCHresource for each TRP may be determined according to the PUCCH resourceselection process in the above-described intra-slot TDMed separateHARQ-ACK. In addition, the other uplink information may also betransmitted through the allocated PUCCH resource.

On the other hand, when an overlap occurs, case 1 and case 2 describedin FIG. 15A may occur.

Accordingly, when it is determined that the case corresponds to case 1in operation 1570, the terminal may perform an operation accordingly.

On the other hand, if it is determined that the case corresponds to case2 in operation 1580, the terminal may perform an operation accordingly.

Details of the operation according to case 1 and case 2 will bedescribed below.

Returning to the description of FIG. 15A, in case 1, it may bedetermined whether the Rel-15-based PUCCH overlapping processing methodis applicable according to the format of each PUCCH resource andtransmission of SR or CSI through PUCCH resource #3. If SR istransmitted through PUCCH resource #3, the following problem may occurwhen applying the Rel-15-based PUCCH multiplexing method.

It is assumed that one of the PUCCH resources for HARQ-ACK transmissionis PUCCH format 1 and the PUCCH resource #3 for SR transmission is PUCCHformat 1. Hereinafter, for the convenience of description, a PUCCHresource for HARQ-ACK transmission corresponding to PUCCH format 1 isreferred to as PUCCH resource #1.

In this case, if the SR is positive at this time, HARQ-ACK for PUCCHresource #1 should be transmitted through PUCCH resource #3. However,since PUCCH resource #3 is not TDM with PUCCH resource #2, it isnecessary to change the Rel-15-based processing method. Therefore, atleast one of the following methods may be considered to solve the aboveproblem.

-   -   Method 1-1: When intra-slot TDMed separate HARQ-ACK is applied,        the multiplexing rule is changed to drop the SR when overlapping        between PUCCH resource (PUCCH format 1) for HARQ-ACK        transmission and PUCCH resource (PUCCH format 1) for SR        transmission occurs.    -   Method 1-2: When intra-slot TDMed separate HARQ-ACK is applied,        PUCCH format 1 is not configured for HARQ-ACK transmission.    -   Method 1-3: When intra-slot TDMed separate HARQ-ACK is applied,        PUCCH format 1 is not configured for SR transmission.    -   Method 1-4: When intra-slot TDMed separate HARQ-ACK is applied,        the terminal does not expect an overlap between PUCCH resource        (PUCCH format 1) for HARQ-ACK transmission and (PUCCH format 1)        for SR transmission.

On the other hand, when the Rel-15-based PUCCH multiplexing method isapplied, the following problems may occur. It is assumed that the PUCCHresource for HARQ-ACK transmission is not PUCCH format 1. In this case,the same SR information is multiplexed and transmitted in both PUCCHresources for HARQ-ACK transmission. This may be an undesirablesituation in the network. For example, a plurality of TRPs receivingHARQ-ACK may proceed with all of the response procedures for the SRrequest, and thus unnecessary control information transmission andreception and uplink resource allocation may occur. Therefore, there isa need for a method of selecting one of PUCCH resources #1 and #2 andallowing SRs to be multiplexed only for the resource.

Therefore, at least one of the following methods may be considered tosolve the above problem. Specifically, an SR is multiplexed andtransmitted to two PUCCH resources for HARQ-ACK transmission, or an SRmay be multiplexed and transmitted to any one of two PUCCH resources,and the following method may be considered as a method of selecting onePUCCH resource.

-   -   Method 2-1: Selection according to the index or order. For        example, a PUCCH resource transmitted first on a time axis may        be selected, or a PUCCH resource corresponding to a low PRI or a        PUCCH resource corresponding to a low PUCCH resource group may        be selected.    -   Method 2-2: Selection according to maximum payload. For example,        a PUCCH resource having a large maximum payload that may be        transmitted may be preferentially selected.    -   Method 2-3: Selection according to PUCCH format. A long PUCCH        with good coverage may be selected in preference to a short        PUCCH. In addition, PUCCH format 2/3/4 capable of transmitting a        payload exceeding 2 bits may be selected in preference to PUCCH        0/1.    -   Method 2-4: Selection according to TRP. When SR information        needs to be transmitted to a specific TRP, a PUCCH resource        corresponding to the same TRP may be selected. For example, a        PUCCH resource for HARQ-ACK with the same spatial relation info        as PUCCH resource #3 may be selected. Alternatively, the PUCCH        resource in the PUCCH resource group belonging to the TRP        corresponding to the SR may be selected. Alternatively, if the        TRP index is configured in the CORESET where the DCI that        schedules the PDSCH and HARQ-ACK PUCCH transmission is        transmitted, a TRP index corresponding thereto may be configured        for each SR ID, or a TRP index to which all SRs are transmitted        may be assumed to be a specific value, for example, TRP index 0.        Alternatively, a TRP index may be configured in a PUCCH resource        to transmit SR, or a specific value, for example, TRP index 0        may be assumed. At this time, the PUCCH resource corresponding        to the HARQ-ACK having the same value as the TRP index        associated with the above-described SR ID or PUCCH for SR        transmission may be selected. Alternatively, the TRP index may        be expressed as a parameter set for PUCCH power control. As an        example, the TRP index may be expressed by one of the following        values in the following PUCCH-PowerControl IE configured as RRC        or a combination thereof.

 PUCCH-PowerControl ::= SEQUENCE {   deltaF-PUCCH-f0 INTEGER (−16..15)OPTIONAL, - - Need R   deltaF-PUCCH-f1 INTEGER (−16..15) OPTIONAL, - -Need P   deltaF-PUCCH-f2 INTEGER (−16..15) OPTIONAL, - - Need P  deltaF-PUCCH-f3 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f4 INTEGER (−16..15) OPTIONAL, Need R   p0-Set SEQUENCE(SIZE (1..maxNrofPUCCH-P0-PerSet)) P0-PUCCH   OPTIONAL,  - - Need M  pathlossReferenceRSs       SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, - - Need M  twoPUCCH-PC-AdjustmentStates        ENUMERATED {twoStates}OPTIONAL, - - Need S   . . .  }  P0-PUCCH ::=  SEQUENCE { p0-PUCCH-Id  P0-PUCCH-Id, p0-PUCCH-Value    INTEGER (−16..15)  }  P0-PUCCH-Id ::= INTEGER (1..8)  PUCCH-PathlossReferenceRS ::=       SEQUENCE {  pucch-PathlossReferenceRS-Id       PUCCH-PathlossReferenceRS-Id,  referenceSignal     CHOICE {    ssb-Index       SSB-Index,   csi-RS-Index        NZP-CSI-RS-ResourceId }

In more detail, the TRP index may correspond to the p0-PUCCH-Id valueconfigured for PUCCH power control. For example, if p0-PUCCH-Id has avalue between 1 and 4, it may correspond to TRP index 0, and whenp0-PUCCH-Id has a value between 5 and 8, it may correspond to TRPindex 1. The mapping between the range of the p0-PUCCH-Id and the TRPindex may be changed. Alternatively, the TRP index may correspond topathlossReferenceRS configured for PUCCH power control. Alternatively,the TRP index may correspond to a power control adjustment state indexconfigured for PUCCH power control. The power control adjustment stateindex is an indicator indicating the power control state of the PUCCHresource, and may also be expressed by expressions such as closed looppower control index and TRP/panel specific closed loop power controlindex. When the twoPUCCH-PC-AdjustmentStates value of the RRC parameteris configured as twoStates, the power control adjustment state index mayhave one of two values, for example, i0 or i1, where i0 may correspondto TRP index 0, and i1 may correspond to TRP index 1. Theabove-mentioned i0 or i1 may be indicated in the form of closedLoopIndexparameter value in spatial relation info that is activated for eachPUCCH/PUCCH group as follows.

PUCCH-SpatialRelationInfo ::= SEQUENCE {  pucch-SpatialRelationInfoIdPUCCH-SpatialRelationInfoId,  servingCellId ServCellIndex OPTIONAL,  - -Need S  referenceSignal   CHOICE {   ssb-Index     SSB-Index,  csi-RS-Index      NZP-CSI-RS-ResourceId,   srs    SEQUENCE {      resource  SRS- ResourceId,       uplinkBWP  BWP- Id    }  }, pucch-PathlossReferenceRS-Id     PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id  P0-PUCCH-Id,  closedLoopIndex   ENUMERATED { i0, i1 } }

According to the above description, the resource with theclosedLoopIndex parameter included in spatial relation info associatedwith the PUCCH resources configured as i0 may be regarded as a PUCCHresource corresponding to TRP index 0, and the resource with theclosedLoopIndex parameter configured as i1 may be regarded as a PUCCHresource corresponding to TRP index 1.

On the other hand, the power control adjustment state index may beextended to be able to configure two per TRP. Therefore, when the numberof TRPs is supported up to 2, the total configurable power controladjustment state index may be expanded up to 4. For example, as thevalue of the twoPUCCH-PC-AdjustmentStates parameter, for example,FourStates may be configured or new parameters such as thefourPUCCH-PC-AdjustmentStates parameter may be configured. At this time,when the closedLoopIndex parameter included in the spatial relation infois configured as i0 and i1, it may be considered as TRP index 0, andwhen the closedLoopIndex parameter is configured as i2, i3, or a newparameter in the spatial relation info, for example, closedLoopIndexNewparameter is additionally configured, it may be considered as TRPindex 1. In addition, as described above, a connection relationshipbetween PUCCH resource and TRP index may be established.

If the PUCCH resource for the TRP to which the SR to be transmitted isnot selected (e.g., due to the absence of information such as spatialrelation info), the terminal might not multiplex SR and HARQ-ACK. Inthis case, according to the order of HARQ-ACK>SR>CSI, PUCCH resource orUCI with a lower priority may be dropped.

Alternatively, for simplification of the terminal operation, the basestation may appropriately schedule PUCCH resources or instructmultiplexing configuration so that the above-described case does notoccur.

Next, in case 1, if CSI is transmitted through PUCCH resource #3, it maybe determined whether to multiplex between HARQ-ACK and CSI byconfiguring a higher layer. If the multiplexing is configured, thefollowing problems may occur when applying the Rel-15-based PUCCHmultiplexing method.

The same CSI information may be multiplexed and transmitted to bothPUCCH resources for HARQ-ACK transmission, which may result in a wasteof uplink transmission resources and transmission power due to duplicateCSI payload transmission. Therefore, there is a need for a method ofselecting one of PUCCH resources #1 and #2 and allowing CSI to bemultiplexed only for the resource.

In order to solve the above problem, at least one of the followingmethods may be considered.

-   -   Method 3-1: Selection according to index or order. For example,        a PUCCH resource transmitted first on a time axis may be        selected, or a PUCCH resource corresponding to a low PRI or a        PUCCH resource corresponding to a low PUCCH resource group may        be selected.    -   Method 3-2: Selection according to maximum payload. A PUCCH        resource having a large maximum payload that may be transmitted        may be preferentially selected.    -   Method 3-3: Selection according to PUCCH format. A long PUCCH        with good coverage may be selected in preference to a short        PUCCH. In addition, when a subband CSI is reported, PUCCH format        3/4 capable of subband CSI transmission may be selected in        preference to PUCCH format 2 only capable of wideband CSI        transmission.    -   Method 3-4: Selection according to TRP. When only the channel        state for a specific TRP is included in the CSI information, it        may be desirable to multiplex CSI information only on PUCCH        resources to be transmitted to the corresponding TRP. To this        end, for example, PUCCH resource for HARQ-ACK with the same        spatial relation info as PUCCH resource #3 may be selected.        Alternatively, the PUCCH resource in the PUCCH resource group        belonging to the TRP corresponding to the CSI information may be        selected. Alternatively, if the TRP index is configured in the        CORESET where the DCI that has scheduled the PDSCH and HARQ-ACK        PUCCH transmission is transmitted, the TRP index may be        configured in the CSI report/resource configuration or the TRP        index in the PUCCH resource for CSI report transmission. At this        time, a PUCCH resource corresponding to HARQ-ACK having the same        value as the TRP index associated with the aforementioned CSI        PUCCH may be selected. If the PUCCH resource for the TRP to        which the CSI is to be transmitted is not selected, the terminal        may not multiplex the CSI with other UCIs. In this case,        according to the order of HARQ-ACK>SR>CSI, a PUCCH resource or        UCI with a lower priority may be dropped. When multiple CSIs        overlap, priority between CSIs may be applied. Alternatively,        when the TRP index is configured in the CSI report/resource        configuration or the TRP index is configured in the PUCCH        resource for transmitting the CSI report, a plurality of CSIs        having different TRP indexes may overlap. At this time, if the        CSI is configured to be multiplexed, for example, when the        above-described multi-CSI-PUCCH-ResourceList is configured, the        TRP index of the PUCCH resource to transmit the multiplexed CSI        may be unclear. The above situation can be prevented by        appropriately scheduling PUCCH resources for CSI report        transmission in the network. Alternatively, if CSI        reports/resources with different TRP indexes are configured or        activated/triggered, multi-CSI-PUCCH-ResourceList might not be        expected to be configured. Alternatively, a TRP index may be        configured for each PUCCH resource corresponding to        multi-CSI-PUCCH-ResourceList, or a specific TRP index value, for        example, TRP index 0 may be assumed. Alternatively, in this        case, even if multi-CSI-PUCCH-ResourceList is configured,        multiplexing between overlapping CSI reports is not performed        and dropping according to priority may be performed. The        priority at this time may follow the Rel-15-based CSI report        priority.

Alternatively, the TRP index may be expressed as a parameter set forPUCCH power control. As an example, the TRP index may be expressed byone of the following values in the following PUCCH-PowerControl IEconfigured as RRC or a combination thereof.

 PUCCH-PowerControl ::= SEQUENCE {   deltaF-PUCCH-f0 INTEGER (−16..15)OPTIONAL, - - Need P   deltaF-PUCCH-f1 INTEGER (−16..15) OPTIONAL, - -Need R   deltaF-PUCCH-f2 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f3 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f4 INTEGER (−16..15) OPTIONAL, - - Need R   p0-SetSEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet) OF P0-PUCCH   OPTIONAL,  - -Need M   pathlossReferenceRSs        SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, - - Need M  twoPUCCH-PC-AdjustmentStates         ENUMERATED {twoStates} OPTIONAL,Need S   . . .  }  P0-PUCCH ::=  SEQUENCE {   p0-PUCCH-Id   P0-PUCCH-Id,  p0-PUCCH-Value    INTEGER (−16..15)  }  P0-PUCCH-Id ::=  INTEGER(1..8)  PUCCH-PathlossReferenceRS      SEQUENCE {  pucch-PathlossReferenceRS-Id      PUCCH-PathlossReferenceRS-Id,  referenceSignal     CHOICE {    ssb-Index      SSB Index,   csi-RS-Index       NZP-CSI-RS-ResourceId   } }

In more detail, the TRP index may correspond to the p0-PUCCH-Id valueconfigured for PUCCH power control. For example, if p0-PUCCH-Id has avalue between 1 and 4, it may correspond to TRP index 0, and whenp0-PUCCH-Id has a value between 5 and 8, it may correspond to TRPindex 1. The mapping between the range of the p0-PUCCH-Id and the TRPindex may be changed. Alternatively, the TRP index may correspond topathlossReferenceRS configured for PUCCH power control. Alternatively,the TRP index may correspond to a power control adjustment state indexconfigured for PUCCH power control. The power control adjustment stateindex is an indicator indicating the power control state of the PUCCHresource, and may also be expressed by expressions such as closed looppower control index and TRP/panel specific closed loop power controlindex. The power control adjustment state index may have one of twovalues, for example, i0 or i1, when the twoPUCCH-PC-AdjustmentStatesvalue of the RRC parameter is configured as twoStates, where i0 maycorrespond to TRP index 0, and i1 may correspond to TRP index 1. Theabove-mentioned i0 or i1 may be indicated in the form of aclosedLoopIndex parameter value in spatial relation info that isactivated for each PUCCH/PUCCH group as follows.

PUCCH-SpatialRelationInfo ::= SEQUENCE {  pucch-SpatialRelationInfoIdPUCCH-SpatialRelationInfoId,  servingCellId ServCellIndex OPTIONAL,  - -Need S  referenceSignal  CHOICE {   ssb-Index    SSB-Index,  csi-RS-Index     NZP-CSI-RS-ResourceId,   srs   SEQUENCE {     resource   SRS- ResourceId,      uplinkBWP  BWP-Id   }  }, pucch-PathlossReferenceRS-Id    PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id,  closedLoopIndex  ENUMERATED { i0, i1 } }

According to the above description, among the PUCCH resources, theresource with the closedLoopIndex parameter related to spatial relationinfo configured as i0 may be considered as the PUCCH resourcecorresponding to TRP index 0, and the resource with the closedLoopIndexparameter configured as i1 may be considered as the PUCCH resourcecorresponding to TRP index 1.

On the other hand, the power control adjustment state index may beextended to be able to configure two per TRP. Therefore, when the numberof TRPs supported is a maximum of 2, the total configurable powercontrol adjustment state index may be expanded to 4. For example, as thevalue of the twoPUCCH-PC-AdjustmentStates parameter, for example,FourStates may be configured or new parameters such as thefourPUCCH-PC-AdjustmentStates parameter may be configured. At this time,when the closedLoopIndex parameter related to spatial relation info isconfigured as i0 and i1, it may be considered as TRP index 0, and theclosedLoopIndex parameter is configured as i2 and 3 or a new parameterin the spatial relation info, for example, the closedLoopIndexNewparameter is additionally configured, it may be considered as TRPindex 1. In addition, as described above, a connection relationshipbetween PUCCH resource and TRP index can be established.

However, if CSI is transmitted through PUCCH resource #3, andmultiplexing between HARQ-ACK and CSI is configured, a method ofmultiplexing and transmitting the same CSI information to both PUCCHresources may be used.

Alternatively, for simplification of the terminal operation, the basestation may appropriately schedule PUCCH resources or instructmultiplexing configuration so that the above-described case does notoccur. For example, when the above-described simultaneous-HARQ-ACK-CSIis configured, the terminal might not expect a situation in which CSI istransmitted through PUCCH resource #3 in Case 1.

In case 2, beams between overlapped PUCCH resources may be different.This can be interpreted as meaning that the TRP to which the UCI istransmitted may be different through the overlapped PUCCH resource. Ifmultiplexing between corresponding PUCCH resources is configured, aproblem occurs in that some of the multiplexed UCIs may be transmittedto an unintended TRP. To solve this, at least one of the followingmethods may be considered.

-   -   Method 4-1: This method follows the beam applied to the PUCCH        corresponding to the high priority UCI among the multiplexed        UCIs. At least the high priority UCI may be transmitted to the        desired TRP therethrough. The UCI priority may be        HARQ-ACK>SR>CSI. When multiple CSIs overlap, priority between        CSIs may be applied.    -   Method 4-2: When the beams between the overlapped PUCCHs are        different, multiplexing might not be performed, which may take        priority over the upper layer configuration. Accordingly, only        one of the overlapped PUCCHs may be selected and transmitted,        and the rest may be dropped, and the PUCCH selection may follow        the priority between UCIs contained in the overlapped PUCCHs.        The UCI priority may be HARQ-ACK>SR>CSI. When multiple CSIs        overlap, priority between CSIs may be applied. The        above-described PUCCH beam may be indicated through PUCCH        spatial relation info. Alternatively, the above-described PUCCH        beam may be replaced with a TRP to transmit PUCCH, where TRP may        be represented by PUCCH spatial relation info, PUCCH resource        group, TRP index, and the like. For example, when a TRP index is        configured in a CORESET where DCIs scheduled for PDSCH and        HARQ-ACK PUCCH transmission are transmitted, a TRP index may be        configured in a CSI report/resource configuration or a TRP index        in a PUCCH resource for CSI report transmission. At this time,        the PUCCH resource corresponding to the CSI having the same        value as the TRP index associated with the aforementioned        HARQ-ACK PUCCH may be selected.

Alternatively, the TRP index, which may be configured in a CSI report orPUCCH resource for SR or HARQ-ACK transmission, may be expressed as aparameter configured for PUCCH power control. As an example, the TRPindex may be expressed as one of the following values in the followingPUCCH-PowerControl IE configured as RRC or a combination thereof.

 PUCCH-PowerControl ::= SEQUENCE {   deltaF-PUCCH-f0 INTEGER (−16..15)OPTIONAL, - - Need P   deltaF-PUCCH-f1 INTEGER (−16..15) OPTIONAL, - -Need R   deltaF-PUCCH-f2 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f3 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f4 INTEGER (−16..15) OPTIONAL, - - Need R   p0-Set SEQUENCE (SIZE (1. maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH  OPTIONAL,  - - Need M   pathlossReferenceRSs        SEQUENCE (SIZE(1..maxNrofPUCCH- PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRSOPTIONAL, - - Need M   twoPUCCH-PC-AdjustmentStates         ENUMERATED{twoStates} OPTIONAL, - - Need S   . . .  }  P0-PUCCH ::=  SEQUENCE {  p0-PUCCH-Id   P0-PUCCH-Id,   p0-PUCCH-Value    INTEGER (−16..15)  } P0-PUCCH-Id ::=  INTEGER (1..8)  PUCCH-PathlossReferenceRS ::=     SEQUENCE {   pucch-PathlossReferenceRS-Id     PUCCH-PathlossReferenceRS-Id,   referenceSignal     CHOICE {   ssb-Index      SSB-Index,    csi-RS-Index       NZP-CSI-RS-ResourceId  } }

In more detail, the TRP index may correspond to the p0-PUCCH-Id valueconfigured for PUCCH power control. For example, if p0-PUCCH-Id has avalue between 1 and 4, it may correspond to TRP index 0, and whenp0-PUCCH-Id has a value between 5 and 8, it may correspond to TRPindex 1. The mapping between the p0-PUCCH-Id range and the TRP index maybe changed. Alternatively, the TRP index may correspond topathlossReferenceRS configured for PUCCH power control. Alternatively,the TRP index may correspond to a power control adjustment state indexconfigured for PUCCH power control. The power control adjustment stateindex is an indicator indicating the power control state of the PUCCHresource, and may also be referred to in an expression such as closedloop power control index or TRP/panel specific closed loop power controlindex. The power control adjustment state index may have one of twovalues, for example, i0 or i1, when the twoPUCCH-PC-AdjustmentStatesvalue of the RRC parameter is configured as twoStates, where i0 is TRPindex 0 and i1 may correspond to TRP index 1. The above-mentioned i0 ori1 may be indicated in the form of closedLoopIndex parameter value inspatial relation info activated by PUCCH/PUCCH group as follows.

PUCCH-SpatialRelationInfo ::= SEQUENCE {  pucch-SpatialRelationInfoIdPUCCH-SpatialRelationInfoId,  servingCellId ServCellIndex OPTIONAL,  - -Need S  referenceSignal  CHOICE {   ssb-Index    SSB-Index,  csi-RS-Index     NZP-CSI-RS-ResourceId,   srs   SEQENCE {     resource   SRS- ResourceId,      uplinkBWP  BWP-Id   }  }, pucch-PathlossReferenceRS-Id    PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id,  closedLoopIndex  ENUMERATED { i0, i1 } }

According to the above description, among the PUCCH resources, aresource with closedLoopIndex parameter related to spatial relation infoconfigured as i0 may be considered as a PUCCH resource corresponding toTRP index 0, and a resource with closedLoopIndex parameter configured asi1 may be considered as PUCCH resource corresponding to TRP index 1. Onthe other hand, the power control adjustment state index may be extendedto be able to configure two per TRP. Therefore, when the number of TRPssupported is a maximum of 2, the total configurable power controladjustment state index may be expanded to 4. For example, as the valueof the twoPUCCH-PC-AdjustmentStates parameter, for example, FourStatesmay be configured or new parameters such as thefourPUCCH-PC-AdjustmentStates parameter may be configured. At this time,when the closedLoopIndex parameter related to the spatial relation infois configured as i0 and i1, it may be considered as the TRP index 0, andwhen the closedLoopIndex parameter is configured as i2 and i3, or a newparameter in the spatial relation info, for example, closedLoopIndexNewparameter, it may be considered as TRP index 1. In addition, asdescribed above, a connection relationship between PUCCH resource andTRP index can be established.

If the TRP index is configured in the CSI report/resource configurationor the TRP index is configured in the PUCCH resource for transmission ofthe CSI report, a plurality of CSIs having different TRP indexes mayoverlap. At this time, if the CSI is configured to be multiplexed, forexample, when the above-described multi-CSI-PUCCH-ResourceList isconfigured, the TRP index of the PUCCH resource to transmit themultiplexed CSI may be unclear. The above situation can be prevented byappropriately scheduling PUCCH resources for CSI report transmission inthe network. Alternatively, if CSI reports/resources with different TRPindexes are configured or activated/triggered,multi-CSI-PUCCH-ResourceList might not be expected to be configured.Alternatively, a TRP index may be configured for each PUCCH resourcecorresponding to multi-CSI-PUCCH-ResourceList, or a specific TRP indexvalue, for example, TRP index 0 may be assumed. Alternatively, in thiscase, even if multi-CSI-PUCCH-ResourceList is configured, multiplexingbetween overlapping CSI reports is not performed, and dropping accordingto priority may be performed. The priority at this time may follow theRel-15-based CSI report priority.

-   -   Method 4-3: In order to simplify the terminal operation, the        base station may appropriately schedule PUCCH resources so that        the overlapped PUCCH beam/TRP does not occur in different cases.

At this time, the TRP or TRP index may be classified by the methoddescribed in Method 4-2. For example, the TRP index may be configuredfor each PUCCH resource. Meanwhile, a TRP index might not be configuredin the PUCCH resource for HARQ-ACK transmission or might not be usedeven if it is configured. Instead, the TRP index configured in theCORESET where the DCI that scheduled the PUCCH transmission istransmitted may be actually used. In addition, the terminal might notexpect that the TRP index configured for each PUCCH resource isdifferent from the TRP index value configured in the CORESET where theDCI that schedules the PUCCH transmission is transmitted.

For example, the TRP index configured for each PUCCH resource may beexpressed in a parameter configured for PUCCH power control. As anexample, the TRP index may be expressed in one of the following valuesin the following PUCCH-PowerControl IE configured as RRC or acombination thereof.

 PUCCH-PowerControl ::= SEQUENCE {   deltaF-PUCCH-f0 INTEGER (−16..15)OPTIONAL, - - Need P   deltaF-PUCCH-f1 INTEGER (−16..15) OPTIONAL, - -Need R   deltaF-PUCCH-f2 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f3 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f4 INTEGER (−16..15) OPTIONAL, - - Need R   p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH  OPTIONAL,  - - Need M   pathlossReferenceRSs        SEQUENCE (SIZE(1..maxNrofPUCCH- PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRSOPTIONAL, - - Need M twoPUCCH-PC-AdjustmentStates         ENUMERATED{twoStates}    . . .  }  P0-PUCCH ::=  SEQUENCE {    p0-PUCCH-Id  P0-PUCCH-Id,    p0-PUCCH-Value    INTEGER (−16..15)  }  P0-PUCCH-Id::=  INTEGER (1..8)  PUCCH-PathlossReferenceRS      SEQUENCE {   pucch-PathlossReferenceRS-Id      PUCCH-PathlossReferenceRS-Id,   referenceSignal     CHOICE {    ssb-Index      SSB-Index,   csi-RS-Index       NZP-CSI-RS-ResourceId   } }

In more detail, the TRP index may correspond to the p0-PUCCH-Id valueconfigured for PUCCH power control. For example, if p0-PUCCH-Id has avalue between 1 and 4, it may correspond to TRP index 0, and whenp0-PUCCH-Id has a value between 5 and 8, it may correspond to TRPindex 1. The mapping between the p0-PUCCH-Id range and the TRP index maybe changed. Alternatively, the TRP index may correspond topathlossReferenceRS configured for PUCCH power control. Alternatively,the TRP index may correspond to a power control adjustment state indexconfigured for PUCCH power control. The power control adjustment stateindex is an indicator indicating the power control state of the PUCCHresource, and may also be referred to as a closed loop power controlindex, TRP/panel specific closed loop power control index, or the like.The power control adjustment state index may have one of two values whenthe twoPUCCH-PC-AdjustmentStates value of the RRC parameter isconfigured as twoStates, for example, a value indicated by i0 or i1,where i0 may correspond to TRP index 0 and i1 may correspond to TRPindex 1. The above-mentioned i0 or i1 may be indicated in the form ofclosedLoopIndex parameter value in spatial relation info activated byPUCCH/PUCCH group as follows.

PUCCH-SpatialRelationInfo ::= SEQUENCE {  pucch-SpatialRelationInfoIdPUCCH-SpatialRelationInfoId,  servingCellId ServCellIndex OPTIONAL,  - -Need S  referenceSignal  CHOICE {   ssb-Index     SSB-Index,  csi-RS-Index NZP-CSI-RS-ResourceId,   srs    SEQUENCE {      resource  SRS- ResourceId,      uplinkBWP  BWP-Id   }  }, pucch-PathlossReferenceRS-Id     PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id,  closedLoopIndex  ENUMERATED { i0, i1 ] }

According to the above description, among the PUCCH resources, theresource with closedLoopIndex parameter related to spatial relation infoconfigured as i0 may be regarded as a PUCCH resource corresponding toTRP index 0, and the resource with closedLoopIndex parameter configuredas i1 may be regarded as PUCCH resource corresponding to TRP index 1.Meanwhile, the power control adjustment state index may be extended tobe able to configure two per TRP. Therefore, when the number of TRPssupported is a maximum of 2, the total configurable power controladjustment state index may be expanded to 4. For example, as the valueof the twoPUCCH-PC-AdjustmnentStates parameter, for example, FourStatesmay be configured or new parameters such as thefourPUCCH-PC-AdjustmentStates parameter may be configured. At this time,when the closedLoopIndex parameter related to the spatial relation infois configured as i0 and i1, it may be regarded as TRP index 0, and whenthe closedLoopIndex parameter is configured as i2, i3 or a new parameterin the spatial relation info, for example, the closedLoopIndexNewparameter is additionally configured, it may be regarded as TRP index 1.In addition, as described above, a connection relationship between PUCCHresource and TRP index can be established.

Alternatively, when the beam/TRP between overlapping PUCCHs isdifferent, the base station may instruct multiplexing configuration sothat multiplexing is not performed. For example, when theabove-described simultaneousHARQ-ACK-CSI is configured, the terminalmight not expect a situation in which the PUCCH resource in whichHARQ-ACK is transmitted and the PUCCH resource in which CSI istransmitted overlap in Case 2. At this time, the inter-PUCCH beam/TRPmay indicate the above-described TRP index.

In the case of intra-slot TDMed separate HARQ-ACK, constraints forsimplifying the overlap processing method between PUCCHs may beconfigured. For example, the PUCCH format of the PUCCH resource forHARQ-ACK transmission may be limited, and the format may be a shortPUCCH, that is, format 0 and format 2 or some of them. It is alsopossible to be limited to a long PUCCH or some of them. Alternatively,in the case of Intra-slot TDMed separate HARQ-ACK, multiplexing betweenHARQ-ACK and CSI is not expected, or it is possible to ignore themultiplexing between HARQ-ACK and CSI and to always drop overlappingCSIs.

Meanwhile, the above-mentioned method can be similarly applied even whenmulti-slot repetition is configured. Therefore, for details, refer tothe above.

Alternatively, when multi-slot repetition is configured, multiplexing isnot allowed between overlapping PUCCHs similar to Rel-15, and the PUCCHresource or UCI with a low priority may be dropped from overlappingslots depending on the priority of HARQ-ACK>SR>CSI. Accordingly, whenmultiple CSIs are multiplexed, priority between CSIs may be applied.

Meanwhile, even when the PUCCH and the PUSCH overlap, multiplexing ordropping may occur. In this case, the PUCCH and the PUSCH may bescheduled in the same serving cell or component carrier (CC), or may bescheduled in the same cell group or other serving cells/CCs belonging tothe same PUCCH group. At this time, a case in which Multiple PUCCH andsingle PUSCH for HARQ-ACK transmission similar to Case 1 overlap withinthe same cell group or the same PUCCH group, single PUCCH and singlePUSCH for HARQ-ACK/SR/CSI transmission similar to Case 2 overlap, ormultiple PUSCHs scheduled in multiple serving cells/CC andsingle/multiple PUSCHs overlap may occur. At this time, the TRP index isconfigured for each CORESET where DCIs for scheduling PUSCHs aretransmitted in each serving cell/CC, and the TRP index may be configuredfor PUCCHs overlapping these PUSCHs. When multiplexing between theoverlapped PUCCH and PUSCH, the PUCCH may be multiplexed on the PUSCHcorresponding to the lowest serving cell/CC index among PUSCHscorresponding to the same value as the TRP index of the PUCCH. If thereis no PUSCH corresponding to the same value as the TRP index of thecorresponding PUCCH, the corresponding PUCCH may be dropped or the PUSCHmay be dropped according to a preset priority. For example, when thePUCCH includes HARQ-ACK the PUSCH is dropped, and when the PUCCHincludes the CSI and the PUSCH also includes the CSI, the PUCCH may bedropped. If the TRP index is not configured in the PUSCH, dropping ormultiplexing may be performed according to the rules configured inRel-5.

At this time, the TRP or TRP index of the PUCCH may be obtainedaccording to the above-described method. For example, the TRP index maybe expressed as a parameter configured for PUCCH power control. As anexample, the TRP index may be expressed as one of the following valuesin the following PUCCH-PowerControl IE configured as RRC or acombination thereof.

 PUCCH-PowerControl : := SEQUENCE {   deltaF-PUCCH-f0 INTEGER (−16..15)OPTIONAL, - - Need R   deltaF-PUCCH-f1 INTEGER (−16..15) OPTIONAL, - -Need R   deltaF-PUCCH-f2 INTEGER (−16..15) OPTIONAL, - - Need R  deltaF-PUCCH-f3 INTEGER (−16..15) OPTIONAL, - - Need P  deltaF-PUCCH-f4 INTEGER (−16..15) OPTIONAL, - - Need P   p0 Set  SEQUENCE SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH  OPTIONAL,  - - Need M   pathlossReferenceRSs        SEQUENCE (SIZE(1..maxNrofPUCCH- PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRSOPTIONAL, - - Need M   twoPUCCH-PC-AdjustmentStates         ENUMERATED{twoStates} OPTIONAL, - - Need S  . . .  }  P0-PUCCH ::=  SEQUENCE {  p0-PUCCH-Id    P0-PUCCH-Id,   p0-PUCCH-Value    INTEGER (−16..15)  } P0-PUCCH-Id ::=  INTEGER (1..8)  PUCCH-PathlossReferenceRS     SEQUENCE {   pucch-PathlossReferenceRS-Id     PUCCH-PathlossReferenceRS-Id,   referenceSignal     CHOICE {   ssb-Index      SSB Index,    csi-RS-Index       NZP-CSI-RS-ResourceId  } }

In more detail, the TRP index may correspond to the p0-PUCCH-Id valueconfigured for PUCCH power control. For example, if p0-PUCCH-Id has avalue between 1 and 4, it may correspond to TRP index 0, and whenp0-PUCCH-Id has a value between 5 and 8, it may correspond to TRPindex 1. The mapping between the p0-PUCCH-Id range and the TRP index maybe changed. Alternatively, the TRP index may correspond topathlossReferenceRS configured for PUCCH power control. Alternatively,the TRP index may correspond to a power control adjustment state indexconfigured for PUCCH power control. The power control adjustment stateindex is an indicator indicating the power control state of the PUCCHresource, and may also be referred to as an expression such as closedloop power control index or TRP/panel specific closed loop power controlindex. The power control adjustment state index may have one of twovalues when the twoPUCCH-PC-AdjustmentStates value of the RRC parameteris configured as twoStates, for example, a value indicated by i0 or i1,where i0 may correspond to TRP index 0, and i1 may correspond to TRPindex 1. The above-mentioned i0 or i1 may be indicated in the form ofclosedLoopIndex parameter value in spatial relation info activated byPUCCH/PUCCH group as follows.

PUCCH-SpatialRelationInfo ::= SEOUENCE {  pucch-SpatialRelationInfoIdPUCCH-SpatialRelationInfoId,  servingCellId ServCellIndex OPTIONAL,  - -Need S  referenceSignal  CHOICE {   ssb-Index    SSB-Index,  csi-RS-Index     NZP-CSI-RS-ResourceId,   srs   SEQUENCE {     resource   SRS- ResourceId,      uplinkBWP  BWP-Id   }  }, pucch-PathlossReferenceRS-Id    PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id,  closedLoopIndex  ENUMERATED { i0, i1 } }

According to the above description, among the PUCCH resources, aresource with closedLoopIndex parameter related to spatial relation infoconfigured as i0 may be regarded as a PUCCH resource corresponding toTRP index 0, and a resource with closedLoopIndex parameter configured asi1 may be regarded as PUCCH resource corresponding to TRP index 1.

On the other hand, the power control adjustment state index may beextended to be able to configure two for each TRP. Therefore, when thenumber of TRPs supported is a maximum of 2, the total configurable powercontrol adjustment state index may be expanded up to 4. For example, asthe value of the twoPUCCH-PC-AdjustmentStates parameter, for example,FourStates may be configured or new parameters such as thefourPUCCH-PC-AdjustmentStates parameter may be configured. At this time,when the closedLoopIndex parameter connected to the spatial relationinfo is configured as i0 and i1, it may be regarded as TRP index 0, andwhen the closedLoopIndex parameter is configured as i2, i3 or a newparameter in the spatial relation info, for example, closedLoopIndexNewparameter, it may be regarded as TRP index 1. In addition, as describedabove, a connection relationship between PUCCH resource and TRP indexcan be established. The connection relationship as above can besimilarly applied between a parameter for PUSCH power control and a TRPindex.

Example 4; Method of Selecting PUCCH Resource for Multi-PDCCH-BasedNC-JT

In this embodiment, when two or more PUCCH resources overlap, a methodof selecting PUCCH resources for multiplexing is proposed.

Case i. When two or more PUCCH resources overlap, when the PUCCH for theHARQ-ACK transmission based on grant is included, as described above,among the PUCCH resources indicated by PRI 9-40, 9-41 for HARQ-ACK inthe PDCCH, only the PUCCH resource (9-31) selected based on PRI (9-41)corresponding to the PDCCH (9-11) transmitted at the last time point maybe selected and transmitted. The PUCCH resource selected at this timemay be selected based on the payload of the UCI to be transmitted asdescribed above. That is, a PUCCH resource set having a minimum payloadnot smaller than the UCI payload may be selected. Next, the PUCCHresource set indicated as PRI in the corresponding PUCCH resource setmay be selected.

If the overlapped PUCCH resource contains UCI transmitted to differentTRPs, a dropping rule as described in Example 3 may be applied.

If the overlapped PUCCH resource contains UCI to be transmitted to thesame TRP, a method is needed to ensure that the selected PUCCH resourcemay also be transmitted to the same TRP according to the payload of themultiplexed UCI. For this, at least one of the following methods may beconsidered.

Method 1. Within the PUCCH resource set, only the PUCCH resourcecorresponding to the target TRP of the UCI to be multiplexed isselected.

Method 2. In the PUCCH resource set, the PUCCH resource that does notcorrespond to the target TRP of the UCI to be multiplexed is excluded.That is, one of the PUCCH resource corresponding to the target TRP andthe PUCCH resource for which the target TRP is not configured areselected.

Method 3. PUCCH resource set and PUCCH resource are selected accordingto the Rel-15-based method described above. At this time, it is assumedthat the target TRP of the selected PUCCH resource corresponds to thetarget TRP of the multiplexed UCI.

At this time, the index of the target TRP of the UCI may be an upperlayer index configured in CORESET where a DCI corresponding to thecorresponding HARQ-ACK is transmitted, for example, a CORESET groupindex or a TRP index in a case of HARQ-ACK. Meanwhile, in the case ofCSI, the index of the target TRP may be a CORESET group index or a TRPindex corresponding to a corresponding CSI report/resourceconfiguration. Alternatively, the HARQ-ACK or CSI may be anexplicit/implicit TRP classification factor corresponding to the PUCCHresource to be transmitted, and the corresponding TRP classificationfactor may be one of a CORESET group index/TRP index/serving cell index.Alternatively, a PUCCH resource group in which the corresponding PUCCHresource included or a group/set index corresponding to a PUCCH resourceset may be used as a TRP classification factor.

Meanwhile, the target TRP corresponding to the PUCCH resource may be aTRP classification factor that explicitly/implicitly corresponds to thecorresponding PUCCH resource, and the TRP classification factor may beone of a CORESET group index/TRP index/serving cell index.Alternatively, a PUCCH resource group to which the corresponding PUCCHresource belongs or a group/set index corresponding to a PUCCH resourceset may be used as a TRP classification factor. Alternatively, the thirdembodiment may be represented by one or a combination of theabove-described PUCCH power control parameters, and the parameter may bethe above-described p0-PUCCH-Id value, pathlossReferenceRS, powercontrol adjustment state index. If the power control adjustment stateindex is used, the TRP classification factor may be a corresponding TRPindex from the power control adjustment state index as described above.

When the PUCCH resource selected according to one of the above methodsoverlaps with other PUCCH resources, the above-described UCImultiplexing and PUCCH resource selection process may be (re)applied ifthe target TRP of these PUCCH resources is the same. If the target TRPof these PUCCH resources is different, a dropping rule as described inEmbodiment 3 above may be applied.

Case ii. When two or more PUCCH resources overlap, each of thecorresponding PUCCH resources is a resource for CSI transmission, orwhen a HARQ-ACK based on a configured grant and one or more CSI overlap,as described above, if multiplexing between multiple CSIs is configuredas a higher layer, a PUCCH resource list for CSI multiplexing configuredas a higher layer, for example, all of the multiplexed UCI payloads in amulti-CSI-PUCCH-ResourceList may be transmitted, and UCI payload may betransmitted after selecting one resource with the lowest index. If thereis no resource that may transmit all of the multiplexed UCI payloads inthe list, the resource with the largest index is selected and the numberof CSI reports that may be transmitted to the resource is transmitted.

If the overlapped PUCCH resource contains UCI transmitted to differentTRPs, a dropping rule as described in Example 3 may be applied.

If the overlapped PUCCH resource contains UCI to be transmitted to thesame TRP, a method is needed to ensure that the selected PUCCH resourcemay also be transmitted to the same TRP according to the payload of themultiplexed UCI. For this, at least one of the following methods may beconsidered.

Method 1 In the multi-CSI-PUCCH-ResourceList, select only the PUCCHresource corresponding to the target TRP of the UCI to be multiplexed.

Method 2. In the multi-CSI-PUCCH-ResourceList, PUCCH resources that donot correspond to the target TRP of the UCI to be multiplexed areexcluded. That is, one of the PUCCH resource corresponding to the targetTRP and the PUCCH resource for which the target TRP is not configuredare selected.

Method 3. Select PUCCH resource in multi-CSI-PUCCH-ResourceListaccording to the Rel-15-based method described above. At this time, itis assumed that the target TRP of the selected PUCCH resourcecorresponds to the target TRP of the multiplexed UCI.

At this time, the target TRP of the UCI and the target TRP of the PUCCHresource may be identified according to the method described above(e.g., Case i).

When the PUCCH resource selected according to one of the above methodsoverlaps with other PUCCH resources, if the target TRP of theoverlapping PUCCH resources is the same, the above-described UCImultiplexing and PUCCH resource selection process may be reapplied. Ifthe target TRP of these PUCCH resources is different, a dropping rule asdescribed in Embodiment 3 above may be applied.

Case iii. In the case of overlap between PUCCH resource and PUSCH, inRel-15, a procedure for transmitting PUSCH only after multiplexing UCIof PUCCH to PUSCH or dropping PUSCH without PUCCH-PUSCH multiplexing isdescribed. At this time, PUCCH and PUSCH where the overlap occurs maybelong to the same serving cell, or may belong to the same cell group oranother serving cell belonging to the same PUCCH group.

If the overlapped PUCCH resource and the target TRP of the PUSCH aredifferent, a dropping rule similar to that described in (e.g.,Embodiment 3) may be applied.

If the overlapped PUCCH resource and the target TRP of the PUSCH are thesame, there is a need for a method to ensure that the multiplexed PUSCHmay also be designated as the same target TRP. For this, at least one ofthe following methods may be considered.

Method 1. Within the PUCCH and the overlapped PUSCH, one PUSCHcorresponding to the target TRP of the UCI to be multiplexed is selectedaccording to a predetermined rule. The rule may be the same as the ruledescribed in Embodiment 3.

Method 2. Within the PUCCH and the overlapped PUSCH, PUSCH that does notcorrespond to the target TRP of the UCI to be multiplexed is excluded.That is, one of the PUSCH corresponding to the target TRP and the PUSCHfor which the target TRP is not configured are selected. The rule may bethe same as the rule described in Embodiment 3.

Method 3. According to the Rel-IS-based method, the PUSCH to bemultiplexed is selected regardless of whether the target TRP value ofthe PUSCH or the target TRP is configured. At this time, it may beassumed that the target TRP of the selected PUSCH corresponds to thetarget TRP of the multiplexed UCI. At this time, the target TRP of theUCI and the target TRP of the PUCCH resource may be identified accordingto the method described above (e.g., Case i). The target TRP of thePUSCH may be identified through the TRP index configured in the CORESETwhere the DCI that schedules the PUSCH is transmitted, or may beidentified through a beam for transmission of the corresponding PUSCH,for example, TPMI indicated by DCI scheduling the corresponding PUSCH orspatialRelationInfo connected to SRI or SRS specified as SRI.

When the selected PUSCH overlaps with other PUCCH resources according toone of the above methods, if the target TRPs of these PUSCHs and PUCCHresources are the same, the multiplexing process described above may bereapplied. If the target TRPs of these PUSCH and PUCCH resources aredifferent, a dropping rule as described in Embodiment 3 above may beapplied.

Meanwhile, in the method proposed in the disclosure, some components maybe omitted and only some components may be included without detractingfrom the essence of the disclosure.

In addition, the method proposed in the disclosure may be performed incombination with some or all of the contents included in each embodimentwithout detracting from the essence of the disclosure.

Embodiment; Method of Generating a HARQ-ACK Codebook for RepetitiveTransmission NC-JT

NC-JT may be used to improve the reliability of PDSCH repeattransmission. Repeated transmission of NC-JT PDSCH may be performedthrough different time resources. For example, the PDSCH may berepeatedly transmitted for each slot over multiple slots, or the PDSCHmay be repeatedly transmitted within one slot. A single PDCCH may beused to schedule the repetitive transmission. The DCI of the PDCCH mayindicate a list of all TRPs participating in repetitive transmission.The list of TRPs to be repeatedly transmitted may be indicated in theform of a TCI state list, and the length of the TCI state list may bechanged dynamically.

When the PDSCH is repeatedly transmitted over multiple slots, the timeand frequency resources of the first PDSCH transmitted are indicated byDCI, and the time and frequency resources in the slots allocated to thePDSCH repeatedly transmitted for each slot may be the same. If thenumber of repetitive transmissions is greater than the number of TCIstates, a specific pattern may be followed when the TCI state is appliedto each repetition slot. For example, if the number of repetitivetransmissions is 4 and TCI state indexes 1 and 2 are indicated, the TCIstate may be applied to each of the transmission slots according to thepattern of 1, 2, 1, 2 or the pattern of 1, 1, 2, 2. In addition, thenumber of repetitive transmissions may be dynamically indicated throughDCI/MAC-CE. For example, the number of repetitive transmissions may beindicated through a time domain resource allocation field indicated byDCI. For example, in addition to the value indicated in the current NRthrough the time domain resource allocation field of DCI, for example,the values of K0, S, L, etc. described above in FIG. 8, the number ofrepetitive transmissions may be indicated together.

When a PDSCH is repeatedly transmitted in one slot, time and frequencyresources of the first PDSCH transmitted in the slot may be indicated byDCI, and symbol length and frequency resources allocated for each PDSCHrepeatedly transmitted may be the same. The repetitively transmittedPDSCH offset may be configured in a unit of symbols. For example, as areference to the last symbol of the first repetitive transmission PDSCH,the next repetitive transmission PDSCH may be transmitted after a symbolseparated by a configured offset.

For the convenience of description, the repetitive transmission methodhas been described with NC-JT as an example, but the repetitivetransmission method is similarly applicable to a single TRP-basedtransmission. For example, a method in which the number of repetitivetransmissions is dynamically indicated through a time domain resourceallocation field indicated by DCI is similarly applicable to a singleTRP-based transmission.

When repetitive transmission is configured according to the aboveembodiment, HARQ-ACK codebook generation methods may be different foreach repetitive transmission method. That is, different HARQ-ACKcodebook generation methods may be applied according to repeatedtransmission in a slot or repeated transmissions over multiple slots. Inthis embodiment, for convenience of description, a description isfocused on a type 1 HARQ-ACK codebook.

FIG. 16A illustrates a view for type 1 HARQ-ACK codebook methods foreach PDSCH repetitive transmission across multiple slots, a PDSCHrepetitive transmission within a single slot, and no repetitivetransmission according to an embodiment, FIG. 16B is a view illustratingtype 1 HARQ-ACK codebook methods for each PDSCH repetitive transmissionacross multiple slots, a PDSCH repetitive transmission within a singleslot, and no repetitive transmission according to an embodiment, andFIG. 16C illustrates a view for type 1 HARQ-ACK codebook methods foreach PDSCH repetitive transmission across multiple slots, a PDSCHrepetitive transmission within a single slot, and no repetitivetransmission according to an embodiment.

First, when there is no repetitive transmission (16-00), a set M_(A,c)of a reception candidate case may be configured according to thepseudo-code 1, and HARQ-ACK feedback bit may be determined according towhether a PDSCH corresponding to each reception candidate in the setM_(A,c) is received according to pseudo-code 2. Whether to receive PDSCH#1 16-10 and PDSCH #2 16-20 is composed of HARQ-ACK codebooks 16-40,respectively, and may be transmitted as PUCCH resources 16-30 or PUSCHresources.

Next, when repetitive transmission in a slot is configured (16-50), aset M_(A,c) of a reception candidate case may be configured according tothe pseudo-code 1, and the HARQ-ACK feedback bit may be determinedaccording to whether each reception candidate in the set M_(A,c)according to the pseudo-code 2 may be determined according to whether aPDSCH corresponding to each reception candidate in the set M_(A,c) isreceived according to pseudo-code 2. On the other hand, in thepseudo-code 2, the HARQ-ACK feedback bit is determined according towhether the repetitive PDSCH is received for the first repetitivelytransmitted PDSCH, while the HARQ-ACK feedback bit is omitted or thecorresponding PDSCH for the second and subsequent PDSCH, or in the caseof a reception candidate corresponding to, that is, a HARQ-ACK feedbackbit may be determined as a NACK at a position corresponding to acorresponding PDSCH among M_(A,c). In addition, when it is configured asto whether the intra-slot repetitive transmission is performed,repetitive transmissions over multiple slots might not be configured atthe same time, and thus, in this case, the number of transmission slotsmay be regarded as one slot.

Next, when repetitive transmission is configured over multiple slots(16-90), the HARQ-ACK feedback bit of the repeated transmission PDSCH16-92 may be transmitted to the PUCCH 16-95 transmitted to the slotcorresponding to the K1 value from the last slot where the PDSCH isrepeatedly transmitted. When the HARQ-ACK is transmitted according tothe pseudo-code 1 and the pseudo-code 2 with respect to the PUCCH(16-94) of the remaining slots, the HARQ-ACK feedback bit may bedetermined as a NACK at a reception candidate corresponding to therepetitively transmitted PDSCH, that is, a position corresponding to thecorresponding PDSCH among M_(A,c).

FIG. 17 illustrates a terminal structure in a wireless communicationsystem according to an embodiment.

Referring to FIG. 17, the terminal may include a transceiver 17-00, amemory 17-05, and a processor 17-10. According to the communicationmethod of the above-described terminal, the transceiver 17-00 and theprocessor 17-10 of the terminal may operate. However, the components ofthe terminal are not limited to the above-described examples. Forexample, the terminal may include more components or fewer componentsthan the aforementioned components. In addition, the transceiver 17-00,the memory 17-05, and the processor 17-10 may be implemented in the formof single chip.

The transceiver 17-00 may transmit and receive a signal to and from abase station. Here, the signal may include control information and data.To this end, the transceiver 17-00 may include an RF transmitter thatup-converts and amplifies the frequency of the transmitted signal, an RFreceiver that amplifies the received signal with low noise anddown-converts the frequency. However, this is only an embodiment of thetransceiver 17-00, and the components of the transceiver 17-00 are notlimited to the RF transmitter and the RF receiver.

The transceiver 17-00 may receive a signal through a wireless channel,output the signal to the processor 17-10, and transmit a signal outputfrom the processor 17-10 through the wireless channel.

The memory 17-05 may store programs and data necessary for the operationof the terminal. In addition, the memory 17-05 may store controlinformation or data included in signals transmitted and received by theterminal. The memory 17-05 may include a storage medium such as a ROM, aRAM, a hard disk, a CD-ROM and a DVD, or a combination of storage media.In addition, a plurality of memories 17-05 may be provided.

In addition, the processor 17-10 may control a series of processes sothat the terminal operates according to the above-described embodiment.For example, the processor 17-10 may control a component of the terminalto receive a plurality of PDSCH at the same time by receiving a DCIcomposed of two layers. There may be a plurality of processors 17-10,and the processors 17-10 may perform component control operations of theterminal by executing a program stored in the memory 17-05.

FIG. 18 illustrates a structure of a base station in a wirelesscommunication system according to an embodiment.

Referring to FIG. 18, the base station may include a transceiver 18-00,a memory 18-05, and a processor 18-10. Depending on the communicationmethod of the base station, the transceiver 18-00 and the processor18-10 of the base station may operate. However, the components of thebase station are not limited to the examples described above. Forexample, the base station may include more or less components than theabove-described components. In addition, the transceiver 18-00, thememory 18-05, and the processor 18-10 may be implemented in the form ofsingle chip.

The transceiver 18-00 may transmit and receive signals to and from theterminal. Here, the signal may include control information and data. Tothis end, the transceiver 18-00 may be configured with an RF transmitterthat up-converts and amplifies the frequency of the transmitted signal,and an RF receiver that amplifies the received signal with low noise anddown-converts the frequency. However, this is only an embodiment of thetransceiver 18-00, and the components of the transceiver 18-00 are notlimited to RF transmitters and RF receivers. The transceiver 18-00 mayreceive a signal through a wireless channel, output the signal to theprocessor 18-10, and transmit the signal output from the processor 18-10through the wireless channel.

The memory 18-05 may store programs and data necessary for the operationof the base station. Further, the memory 18-05 may store controlinformation or data included in signals transmitted and received by thebase station. The memory 18-05 may include a storage medium such as aROM, a RAM, a hard disk, a CD-ROM and a DVD, or a combination of storagemedia. In addition, a plurality of memories 18-05 may be provided.

The processor 18-10 may control a series of processes so that the basestation may operate according to the above-described embodiments. Forexample, the processor 18-10 may configure two layers of DCIs includingallocation information for multiple PDSCHs and control each component ofthe base station to transmit them. There may be a plurality ofprocessors 18-10, and the processors 18-10 may perform component controloperations of the base station by executing a program stored in thememory 18-05.

Methods disclosed in the claims and/or methods according to variousembodiments described in the specification of the disclosure may beimplemented by hardware, software, or a combination of hardware andsoftware.

When the methods are implemented by software, a computer-readablestorage medium for storing one or more programs (software modules) maybe provided. The one or more programs stored in the computer-readablestorage medium may be configured for execution by one or more processorswithin the electronic device. The at least one program may includeinstructions that cause the electronic device to perform the methodsaccording to various embodiments of the disclosure as defined by theappended claims and/or disclosed herein.

The programs (software modules or software) may be stored innon-volatile memories including a random access memory and a flashmemory, a read only memory (ROM), an electrically erasable programmableread only memory (EEPROM), a magnetic disc storage device, a compactdisc-ROM (CD-ROM), digital versatile discs (DVDs), or other type opticalstorage devices, or a magnetic cassette. Alternatively, any combinationof some or all of them may form a memory in which the program is stored.Further, a plurality of such memories may be included in the electronicdevice.

In addition, the programs may be stored in an attachable storage devicewhich may access the electronic device through communication networkssuch as the Internet, Intranet, Local Area Network (LAN), Wide LAN(WLAN), and Storage Area Network (SAN) or a combination thereof. Such astorage device may access the electronic device via an external port.Further, a separate storage device on the communication network mayaccess a portable electronic device.

In the above-described detailed embodiments of the disclosure, anelement included in the disclosure is expressed in the singular or theplural according to presented detailed embodiments. However, thesingular form or plural form is selected appropriately to the presentedsituation for the convenience of description, and the disclosure is notlimited by elements expressed in the singular or the plural. Therefore,either an element expressed in the plural may also include a singleelement or an element expressed in the singular may also includemultiple elements.

The embodiments of the disclosure described and shown in thespecification and the drawings have been presented to easily explain thetechnical contents of the disclosure and help understanding of thedisclosure, and are not intended to limit the scope of the disclosure.That is, it will be apparent to those skilled in the art that othermodifications and changes may be made thereto on the basis of thetechnical spirit of the disclosure. Further, the above respectiveembodiments may be employed in combination, as necessary. For example,embodiments I and 2 of the disclosure may be partially combined tooperate a base station and a terminal. Further, although the aboveembodiments have been described by way of the FDD LTE system, othervariants based on the technical idea of the embodiments may beimplemented in other systems such as TDD LTE, 5G, and NR systems.

In the drawings in which methods of the disclosure are described, theorder of the description does not always correspond to the order inwhich steps of each method are performed, and the order relationshipbetween the steps may be changed or the steps may be performed inparallel.

Alternatively, in the drawings in which methods of the disclosure aredescribed, some elements may be omitted and only some elements may beincluded therein without departing from the essential spirit and scopeof the disclosure.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method performed by a terminal for transmittinghybrid automatic repeat request (HARQ) information formulti-transmission and reception points (TRPs) in a wirelesscommunication system, the method comprising: receiving, from a basestation, first information on a plurality of repetition numbers andsecond information on a plurality of HARQ feedback timings via radioresource control (RRC) signaling; receiving, from the base station,downlink control information (DCI) including third informationindicating one of the plurality of repetition numbers and fourthinformation indicating one of the plurality of HARQ feedback timings;performing physical downlink shared channel (PDSCH) receptions in aplurality of slots based on a repetition number indicated by the DCI;and transmitting, to the base station, the HARQ information for thePDSCH receptions in a determined based on a last slot of the pluralityof first slots and a HARQ feedback timing indicated by the DCI, whereinthe HARQ information corresponding to a PDSCH reception in a slot otherthan the last slot of the plurality of slots is set to a negativeacknowledgment (NACK).
 2. The method of claim 1, wherein thetransmitting the HARQ information further comprises transmitting anacknowledgment (ACK) in the slot in case that the PDSCH receptions areperformed successfully.
 3. The method of claim 1, wherein a number ofthe HARQ feedback timings is configured to a maximum of
 8. 4. The methodof claim 1, wherein fifth information on a start symbol and a number ofsymbols of the plurality of slots is received via the RRC signaling. 5.A method for receiving hybrid automatic repeat request (HARQ)information for multi-transmission and reception points (TRPs) performedby a base station in a wireless communication system, the methodcomprising: transmitting, to a terminal, first information on aplurality of repetition numbers and second information on a plurality ofHARQ feedback timings via radio resource control (RRC) signaling;transmitting, to the terminal, downlink control information (DCI)including third information indicating one of the plurality ofrepetition numbers and fourth information indicating one of theplurality of HARQ feedback timings; transmitting, to the terminal,physical downlink shared channels (PDSCHs) in a plurality of slots basedon a repetition number indicated by the DCI; and receiving, from theterminal, the HARQ information for the PDSCHs in a slot determined basedon a last slot of the plurality of slots and a HARQ feedback timingindicated by the DCI, wherein HARQ information corresponding to a PDSCHin a slot other than the last slot of the plurality of slots is set to anegative acknowledgment (NACK).
 6. The method of claim 5, wherein anacknowledgment (ACK) is received in the slot in case that PDSCHs aresuccessfully transmitted.
 7. The method of claim 5, wherein a number ofthe HARQ feedback timings is configured to a maximum of
 8. 8. The methodof claim 5, wherein fifth information on a start symbol and a number ofsymbols of the plurality of slots is received via the RRC signaling. 9.A terminal for transmitting hybrid automatic repeat request (HARQ)information for multi-transmission and reception points (TRPs) in awireless communication system, the terminal comprising: a transceiver;and a controller coupled with the transceiver and configured to:receive, from a base station, first information on a plurality ofrepetition numbers and second information on a plurality of HARQfeedback timings via radio resource control (RRC) signaling, receive,from the base station, downlink control information (DCI) includingthird information indicating one of the plurality of repetition numbersand fourth information indicating one of the plurality of HARQ feedbacktimings, perform physical downlink shared channel (PDSCH) receptions ina plurality of first slots based on a repetition number indicated by theDCI, and transmit, to the base station, the HARQ information for thePDSCH receptions in a slot determined based on a last slot of theplurality of slots and a HARQ feedback timing indicated by the DCI,wherein the HARQ information corresponding to a PDSCH reception in aslot other than the last slot of the plurality of slots is set to anegative acknowledgment (NACK).
 10. The terminal of claim 9, wherein thecontroller is configured to transmit an acknowledgment (ACK) in the slotin case that the PDSCH receptions are performed successfully.
 11. Theterminal of claim 9, wherein a number of the HARQ feedback timings isconfigured to a maximum of
 8. 12. The terminal of claim 9, wherein fifthinformation on a start symbol and a number of symbols of the pluralityof slots is received via the RRC signaling.
 13. A base station forreceiving hybrid automatic repeat request (HARO) information formulti-transmission and reception points (TRPs) in a wirelesscommunication system, the base station comprising: a transceiver; and acontroller configured to: transmit, to a terminal, first information ona plurality of repetition numbers and second information on a pluralityof HARQ feedback timings via radio resource control (RRC) signaling,transmit, to the terminal, downlink control information (DCI) includingthird information indicating one of the plurality of repetition numbersand fourth information indicating one of the plurality of HARO feedbacktimings, transmit, to the terminal, physical downlink shared channels(PDSCHs) in a plurality of slots based on a repetition number indicatedby the DCI, and receive, from the terminal, the HARQ information for thePDSCHs in a slot determined based on a last slot of the plurality ofslots and a HARO feedback timing indicated by the DCI, wherein the HARQinformation corresponding to a PDSCH in a slot other than the last slotof the plurality of slots is set to a negative acknowledgment (NACK).14. The base station of claim 13, wherein an acknowledgment (ACK) isreceived in the slot in case that PDSCHs are successfully transmitted.15. The base station of claim 13, wherein a number of the HARQ feedbacktimings is configured to a maximum of
 8. 16. The base station of claim13, wherein fifth information on a start symbol and a number of symbolsof the plurality of slots is received via the RRC signaling.